|
|
|
wxPack Details wxPack Help Current digg.com activity
|
PurposeTo explain how to build wxWidgets with MinGW GCC (3.x.x - 4.x.x) and Microsoft Visual C++ (7.1-8.0) including the toolkit editions.
FilesDetails
Now just zip up the 'lib' directory. NOTE: Please remove *.ilk files if present. Notes
wxBuild_wxWidgets.bat Usage wxBuild_wxWidgets v1.09
Build wxWidgets with the MinGW/Visual C++ Tool chains.
Usage: "wxBuild_wxWidgets.bat <Compiler{MINGW|MINGW4|VCTK|VC71|VC80}>
<BuildTarget{LIB|DLL|ALL|CLEAN|MOVE|NULL}> [Specific Option (See Below)]"
Compiler Options:
MINGW = MinGW Gcc v3.x.x compiler
MINGW4 = MinGW Gcc v4.x.x compiler
VCTK = Visual C++ 7.1 Toolkit
VC71 = Visual C++ 7.1
VC80 = Visual C++ 8.0
BuildTarget Options:
LIB = Builds all the static library targets.
DLL = Builds all the dynamic library targets.
ALL = Builds all the targets (Recommended).
CLEAN = Cleans the solution.
MOVE = Moves the binary files to a compiler specific directory.
This helps to allow for automated builds using compilers
from the same family. (ex. VC 7.1 and VC8.0))
NULL = Used so that you can specify a specific target. (See below)
Specific Options(Used with NULL):
LIB_DEBUG, LIB_RELEASE, LIB_DEBUG_UNICODE, LIB_RELEASE_UNICODE,
LIB_DEBUG_MONO, LIB_RELEASE_MONO, LIB_DEBUG_MONO_UNICODE,
LIB_RELEASE_MONO_UNICODE,
DLL_DEBUG, DLL_RELEASE, DLL_DEBUG_UNICODE, DLL_RELEASE_UNICODE,
DLL_DEBUG_MONO, DLL_RELEASE_MONO, DLL_DEBUG_MONO_UNICODE,
DLL_RELEASE_MONO_UNICODE
Examples:
wxBuild_default.bat MINGW ALL
Builds all targets with MinGW Gcc 3.x.x Compiler.
wxBuild_default.bat MINGW4 ALL
Builds all targets with MinGW Gcc 4.x.x Compiler.
wxBuild_default.bat VCTK LIB
Builds just the static libraries with Visual C++ 7.1 Toolkit.
wxBuild_default.bat VC80 NULL LIB_RELEASE
Builds only the release static library with Visual C++ 8.0 Compiler
|