moonwell-core-vanilla

Files

T

ratkosrb 25b64c7c25 Add support for MinGW and ARM (#322 )

* Add support for mingw compiler and arm platform.

* Change else to elseif in cmake file.

* Add libseh for mingw.

* Fix extractors build.

* Remove static link flags.

* Undo some changes that were not needed.

* Remove debug flag from extractors.

* Add missing readme for libseh.

* Remove not needed acquire on guard.

2019-12-01 15:31:38 +02:00

vmapextract

Fix a ton of warnings found using clang. (#308 )

2019-11-20 20:27:36 +02:00

.gitignore

Initial Commit / Core Files

2017-03-10 00:38:11 +03:00

CMakeLists.txt

Add support for MinGW and ARM (#322 )

2019-12-01 15:31:38 +02:00

make_vmaps.bat

Initial Commit / Core Files

2017-03-10 00:38:11 +03:00

README

Initial Commit / Core Files

2017-03-10 00:38:11 +03:00

README

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/ 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\win
	Resulting binaries will be in contrib\vmap_extractor\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