Skip to content

spring/mingwlibs

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

MinGW libraries for the Spring RTS game engine

README

The files in this package are needed to compile spring with MinGW.

Notes for users

There are two ways of using/setting-up mingwlibs.

  1. The simple one (recommended for new users)

Have them in a folder named mingwlibs where you have extracted the spring source tarball or git repository. This way, SCons or CMake will automatically find the libs. Your directory structure should look like this:

AI/                 Spring AI source code
game/               Output binaries go here
installer/          Scripts to build installer
rts/                Spring source code
mingwlibs/          This package!
mingwlibs/bin/      Executables
mingwlibs/dll/      Dynamic link libraries
mingwlibs/include/  Header files
mingwlibs/jlib/     Java libraries
mingwlibs/lib/      Native import libraries
  1. For multiple spring repositories

This is useful if you have multiple spring repositories, and you do not want to maintain mingwlibs separately for each of them, or if you simple want to keep it away from the spring sources.

Just extract the archive anywhere you want it, eg like this:

C:\mingwlibs\bin
C:\mingwlibs\dll
C:\mingwlibs\include
C:\mingwlibs\jlib
C:\mingwlibs\lib

For the spring build-system to find the libs, you have to specify them in the configure step like this:

CMake

cmake -DMINGWLIBS=C:\mingwlibs [other-options...]

Notes for maintainers

Creating MinGW32 import libraries

Also included is reimp_new.zip, this contains reimp.exe which has been used to create MinGW32 import libraries for DevIL.dll, ILU.dll and ILUT.dll:

reimp DevIL.dll
reimp ILU.dll
reimp ILUT.dll

This creates libdevil.a, libilu.a, libilut.a and a number of .def files. You can throw away the .def files and move the lib*.a files to lib/.

Cross-Compiling Boost

Download the latest boost sources archive.

Due to the nature of boost, it is very likely these steps will have to be adapted in-between versions.

Adjust and run boost_crosscompile.sh.

You should now have both the static libs and the headers of the new boost version in your mingwlibs dir, and are only left to do the git magic to commit, and optionally mention the new version in the list below.

Current versions of included libraries and binaries

Releases

No releases published

Packages

No packages published

Languages