server/contrib/vmap_extractor_v2
Lynx3d cda38d9370 [10163] Update vmap_extractor to support new vmap implementation.
Note: This is not compatible with current assembler, wait for upcoming commits

* Now also supports Linux (CMake) and Visual Studio 2010,
  see README for build and use instructions
* Uses libmpq for now, since at project start stormlib did not work
  properly on 64bit linux.
* Should be a lot faster, a few badly written lines ate most CPU time for
nothing...

Special thanks to arrai and faramir118 for additional code and fixes
2010-07-08 23:09:01 +02:00
..
doc [9989] Use unix styoe line ends in soem files 2010-05-28 02:27:12 +04:00
stormdll [9989] Use unix styoe line ends in soem files 2010-05-28 02:27:12 +04:00
stormlib [9989] Use unix styoe line ends in soem files 2010-05-28 02:27:12 +04:00
stormlibdll [8481] Convert some detected files to unix line ends. 2009-09-10 05:11:36 +04:00
vmapextract [10163] Update vmap_extractor to support new vmap implementation. 2010-07-08 23:09:01 +02:00
win [10163] Update vmap_extractor to support new vmap implementation. 2010-07-08 23:09:01 +02:00
.gitignore [10163] Update vmap_extractor to support new vmap implementation. 2010-07-08 23:09:01 +02:00
CMakeLists.txt [10163] Update vmap_extractor to support new vmap implementation. 2010-07-08 23:09:01 +02:00
README [10163] Update vmap_extractor to support new vmap implementation. 2010-07-08 23:09:01 +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 buid 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