![]() To make it possible to check if this is the case, the library predefines the symbols in the form wxHAS_FEATURE. Some library features may not be always available even if they were selected by the user. The value of this macro corresponds to the compiler version, 1100 is 11. you can use tests such #ifdef VISUALC7 to test for compiler version being precisely 7. For convenience, the symbols VISUALCn are also defined for each major compiler version from 5 to 12, i.e. The value of this macro corresponds to the compiler version: 1020 for 4.2 (the first supported version), 1100 for 5.0, 1200 for 6.0 and so on. Microsoft Visual C++, see also wxCHECK_VISUALC_VERSION. Gnu-Win32 compiler, see also wxCHECK_W32API_VERSIONĮither MinGW32 or MinGW-w64 in either 32 or 64 bits Gnu C++ on any platform, see also wxCHECK_GCC_VERSION The value of the macro corresponds to the compiler version: 500 is 5.0.Įmbedded Visual C++ 4 (can be only used for building wxWinCE) ![]() NET devices (_WIN32_WCE is 400 or greater)īorland C++. Microsoft-powered Windows CE devices, for generic Windows CE applications Microsoft-powered PocketPC devices with touch-screen Small but powerful computer, usually with a keyboard Personal digital assistant, usually with touch screen ![]() Generic mobile devices with phone buttons and a small display Note that not all of these symbols are always defined, it depends on the compiler used. Win64 (mostly same as Win32 but data type sizes are different) Win16 API (not supported since wxWidgets 2.6) Mach-O Architecture (Mac OS X only builds)Īny Windows platform, using any port (see also WXMSW) Mac OS X (with BSD C library), using any port (see also WXOSX) The convention is to use the _WX prefix for these symbols, although this has not always been followed. If you want to test for any port under Mac OS X, including, for example, wxGTK and also wxBase, use DARWIN (see below).If you want to test for any GUI Mac port under OS X, use WXOSX_OR_COCOA.If you want to test for wxOSX on the iPhone, use WXOSX_IPHONE.If you want to test for wxOSX on the desktop, use WXOSX_MAC.And there is the Cocoa port named wxCocoa which has not been updated very actively since beginning 2008. One of them, wxOSX is the successor of the venerable wxMac, it currently exists in three versions: Carbon and Cocoa for the desktop and a very early iPhone port. ![]() There are two wxWidgets ports to Mac OS X. WxUniversal port, always defined in addition to one of the symbols above so this should be tested first. WxX11 ( WXUNIVERSAL will be also defined) Xt mutually exclusive with WX_MOTIF, not implemented in wxWidgets 2.x Stubbed version ('template' wxWin implementation) OS X GUI using any Apple widget framework (Carbon, AppKit or UIKit)Īny Mac OS X port (wxOSX-Carbon, wxOSX-Cocoa or wxCocoa) Notice that for compatibility reasons, this symbol is defined for console applications under Windows as well, but it should only be used in the GUI code while WINDOWS should be used for the platform tests. ![]() Only wxBase, no GUI features (same as wxUSE_GUI = 0) These are preprocessor symbols used in the wxWidgets source, grouped by category (and sorted by alphabetical order inside each category).Īll of these macros except for the wxUSE_XXX variety is defined if the corresponding condition is true and undefined if it isn't, so they should be always tested using #ifdef and not #if. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |