server/contrib/vmap_extractor_v3
Machiavelli 32aede1a82 [12075] Don't check registry for game folder on windows, use relative "Data" dir, similar to linux.
Fixes annoyance when you have multiple wow clients and building vmaps fails for reason that extractor takes path from wrong client even though it is located inside the correct directory

Signed-off-by: stfx <stfx@hotmail.de>
2012-08-02 10:08:40 +02:00
..
vmapextract [12075] Don't check registry for game folder on windows, use relative "Data" dir, similar to linux. 2012-08-02 10:08:40 +02:00
win [11795] Drop support for VC 2005 2011-09-17 19:53:15 +06:00
.gitignore [10463] Clean up the .gitignore files. 2010-09-10 19:29:52 +02:00
CMakeLists.txt [11875] Update Copyright notice to year 2012 2012-01-16 17:43:59 +01:00
make_vmaps.bat [11916] Remove old binaries for extraction 2012-02-06 23:57:24 +01:00
README [10176] Use std::isnan in the hope more non-MS platforms provide it. 2010-07-10 13:54:35 +02:00

Linux:

1. Building

	Because vmap_extractor depends on libmpq for reading mpq files, you will have
	to build libmpq prior to vmap_extractor. Therefore cd to dep/libmpq and execute:

	$ ./autogen.sh
	$ ./configure
	$ make

	After that, cd to contrib/vmap_extractor_v2/ and execute:

	$ cmake .
	$ make

	You should now have an executable file at vmapextract/vmapextractor

2. Extracting

	Use the created executable to extract model information. Change the data path if
	needed.

	$ vmapextract/vmapextractor -d /mnt/windows/games/wow/Data/

	Resulting files will be in ./Buildings

###########################
Windows:

1. Building

	Just build the solution in contrib\vmap_extractor_v2\win
	Resulting binaries will be in contrib\vmap_extractor_v2\bin\$(PlatformName)_$(ConfigurationName)

2. Extracting

	Use the created executable (from command prompt) to extract model information.
	It should find the data path for your client installation through the windows registry,
	but the data path can be specified with the -d option.

	Resulting files will be in .\Buildings