WxWidgets installation and testing

Wxwindowsquickref quick reference:

Http://wiki.codeblocks.org/index.php? Title = wxwindowsquickref # frequently_asked_questions

WxWidgets compilation and simple test

Http://hi.baidu.com/fcl06/blog/item/5233d8efbdaa763fadafd52f.html

-------------------------------------------------------

Execute the build command. The recommended command to use for mingw/GCC is:

mingw32-make -f makefile.gcc BUILD=release SHARED=1 MONOLITHIC=1 UNICODE=1

　　

Build

Build controls whether a debug version (build = Debug) or release version (build = release) of wxWidgets itself is built. in the vast majority of cases you will only need a release version of wxWidgets, since you won't be interesting in debugging wxWidgets itself. you can still create debug builds of your own programs that link to a release build of wxWidgets.

A debug build of wxWidgets creates libraries with a "D" suffix -- for example, "libwxmsw28d. A"/"wxmsw28d_gcc_custom.dll ".

A debug build of wxWidgets creates the folder "mswd" or "mswud" in the wxWidgets library Output Folder.

A release build of wxWidgets creates libraries without the "D" suffix -- for example, "libwxmsw28.a"/"wxmsw28_gcc_custom.dll ".

A release build of wxWidgets creates the folder "MSW" or "mswu" in the wxWidgets library Output Folder.

Shared

Shared controls whether a DLL (shared = 1) or static (shared = 0) version of wxWidgets is built. with a DLL build, compile times are faster and the executable size is smaller. the total size of a single executable plus the wxWidgets DLL is greater, but multiple executables can use the same DLL.

A dll build of wxWidgets creates import libraries (such as libwxmsw28.a) and DLLs (such as wxmsw28_gcc_custom.dll). You must include the DLL when you distribute your program.

A static build of wxWidgets creates static libraries only (such as libwxmsw28.a), and you do not need to distribute a wxWidgets DLL.

Monolithic

Monolithic controls whether a single library (monolithic = 1) or Multiple Component Libraries (monolithic = 0) are built. with a monolithic build, project setup and development are much easier, and you only have one DLL to distribute if you're using a DLL build. with a non-monolithic (multilib) Build, several different libraries are built and you can avoid linking with the entire wxWidgets codebase for programs that don't need it. you do have to ensure that you choose the correct component libraries.

A monolithic build of wxWidgets creates a single wxWidgets import library (such as libwxmsw28.a) and a single DLL (such as wxmsw28_gcc_custom.dll ).

A multilib build of wxWidgets creates multiple import libraries (libwx28_base.a, etc.) and multiple DLLs.

Additional static libraries are always created with any wxWidgets build (libwxexpat. a, libwxjpeg. a, etc .). these libraries do not normally need to be used with DLL builds of wxWidgets, but they are required when using static builds.

Unicode

Unicode controls whether wxWidgets and your program use wide-character strings with Unicode support. most programs for Windows 2000 and later shoshould do so. earlier versions of Windows don't have the necessary Unicode support. you shoshould always use wxwidget's _ ("string") and _ T ("string") macros to ensure that your hardcoded strings are the correct type.

A Unicode (UNICODE = 1) Build of wxWidgets creates libraries with a "U" suffix -- for example, "libwxmsw28u. A"/"wxmsw28u_gcc_custom.dll ".

A Unicode build of wxWidgets creates the folder "mswu" or "mswud" in the wxWidgets library Output Folder.

An ANSI (UNICODE = 0) Build of wxWidgets creates libraries without the "U" suffix -- for example, "libwxmsw28.a"/"wxmsw28_gcc_custom.dll ".

An ANSI build of wxWidgets creates the folder "MSW" or "mswd" in the wxWidgets library Output Folder.