X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/9ceeecb94e9b5e4a5d9f3382e91eb4c1aad1d382..97ad053bffe0fe5d8862578bae4e7492592b5702:/docs/latex/wx/cppconst.tex?ds=inline diff --git a/docs/latex/wx/cppconst.tex b/docs/latex/wx/cppconst.tex index 9e9acaef7d..c573457828 100644 --- a/docs/latex/wx/cppconst.tex +++ b/docs/latex/wx/cppconst.tex @@ -1,4 +1,15 @@ -\section{Preprocesser symbols defined by wxWidgets}\label{cppconst} +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%% Name: cppconst.tex +%% Purpose: Peprocessor symbols +%% Author: +%% Modified by: +%% Created: +%% RCS-ID: $Id$ +%% Copyright: (c) wxWidgets +%% License: wxWindows license +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +\section{Preprocessor symbols defined by wxWidgets}\label{cppconst} These are preprocessor symbols used in the wxWidgets source, grouped by category (and sorted by alphabetical order inside each category). All of @@ -12,7 +23,6 @@ always tested using \texttt{#ifdef} and not \texttt{#if}. \twocolitem{\_\_WINDOWS\_\_}{any Windows, yom may also use \_\_WXMSW\_\_} \twocolitem{\_\_WIN16\_\_}{Win16 API (not supported since wxWidgets 2.6)} \twocolitem{\_\_WIN32\_\_}{Win32 API} -\twocolitem{\_\_WIN95\_\_}{Windows 95 or NT 4.0 and above system (not NT 3.5x)} \twocolitem{\_\_WXBASE\_\_}{Only wxBase, no GUI features (same as \texttt{wxUSE\_GUI} $== 0$)} \twocolitem{\_\_WXCOCOA\_\_}{OS X using Cocoa API} \twocolitem{\_\_WXWINCE\_\_}{Windows CE} @@ -28,7 +38,6 @@ always tested using \texttt{#ifdef} and not \texttt{#if}. \twocolitem{\_\_WXMGL\_\_}{SciTech Soft MGL (\_\_WXUNIVERSAL\_\_ will be also defined)} \twocolitem{\_\_WXMSW\_\_}{Any Windows} -\twocolitem{\_\_WXOS2\_\_}{Identical to \_\_WXPM\_\_} \twocolitem{\_\_WXOSX\_\_}{Any Mac OS X port (either Carbon or Cocoa)} \twocolitem{\_\_WXPALMOS\_\_}{PalmOS} \twocolitem{\_\_WXPM\_\_}{OS/2 native Presentation Manager} @@ -52,7 +61,7 @@ summarize: \begin{itemize} \item If you want to test for all Mac platforms, classic and OS X, you should test both \texttt{\_\_WXMAC\_\_} and \texttt{\_\_WXCOCOA\_\_}. -\item If you want to test for any GUI Mac port under OS X, use +\item If you want to test for any GUI Mac port under OS X, use \texttt{\_\_WXOSX\_\_}. \item If you want to test for any port under Mac OS X, including, for example, wxGTK and also wxBase, use \texttt{\_\_DARWIN\_\_} (see below). @@ -107,20 +116,14 @@ compiler used. \subsection{Hardware type}\label{hardwareconst} -% Note: previous documentation referred to __SMARTPHONE__ as a generic (non-MS-specific) symbol -% but we should go back to using it for a specific SDK, because trying to be -% generic doesn't really work - \begin{twocollist}\itemsep=0pt -\twocolitem{\_\_SMARTPHONE\_\_}{Microsoft-powered mobile devices with phone buttons and a small display} +\twocolitem{\_\_SMARTPHONE\_\_}{Generic mobile devices with phone buttons and a small display} +\twocolitem{\_\_PDA\_\_}{Personal digital assistant, usually with touch screen} +\twocolitem{\_\_HANDHELD\_\_}{Small but powerful computer, usually with a keyboard} \twocolitem{\_\_POCKETPC\_\_}{Microsoft-powered PocketPC devices with touch-screen} \twocolitem{\_\_WINCE\_STANDARDSDK\_\_}{Microsoft-powered Windows CE devices, for generic Windows CE applications} \twocolitem{\_\_WINCE\_NET\_\_}{Microsoft-powered Windows CE .NET devices (\_WIN32\_WCE is 400 or greater)} -% Note to doc writers: these symbols are pretty useless because of the blurred -% dividing lines between these machines, plus they're not actually used. -%\twocolitem{\_\_PDA\_\_}{Personal digital assistant usually with touch screen and -%middle sized screen (not yet defined anywhere)} -%\twocolitem{\_\_HANDHELD\_\_}{Small enough but powerful computer (not yet defined anywhere)} +\twocolitem{WIN32\_PLATFORM\_WFSP}{Microsoft-powered smartphone} \end{twocollist} @@ -131,9 +134,9 @@ compiler used. to the compiler version: $500$ is $5.0$.} \twocolitem{\_\_DJGPP\_\_}{DJGPP} \twocolitem{\_\_DIGITALMARS\_\_}{Digital Mars} -\twocolitem{\_\_GNUG\_\_}{Gnu C++ on any platform, see also +\twocolitem{\_\_GNUG\_\_}{Gnu C++ on any platform, see also \helpref{wxCHECK\_GCC\_VERSION}{wxcheckgccversion}} -\twocolitem{\_\_GNUWIN32\_\_}{Gnu-Win32 compiler, see also +\twocolitem{\_\_GNUWIN32\_\_}{Gnu-Win32 compiler, see also \helpref{wxCHECK\_W32API\_VERSION}{wxcheckw32apiversion}} \twocolitem{\_\_MINGW32\_\_}{MinGW} \twocolitem{\_\_MWERKS\_\_}{CodeWarrior MetroWerks compiler} @@ -159,6 +162,13 @@ also \helpref{wxCHECK\_VERSION}{wxcheckversion}} \twocolitem{wxUSE\_XXX}{if defined as $1$, feature XXX is active (the symbols of this form are always defined, use \#if and not \#ifdef to test for them)} +\twocolitem{WX\_PRECOMP}{is defined if precompiled headers (PCH) are in use. In +this case, \texttt{wx/wxprec.h} includes \texttt{wx/wx.h} which, in turn, +includes a number of wxWidgets headers thus making it unnecessary to include +them explicitly. However if this is not defined, you do need to include them +and so the usual idiom which allows to support both cases is to first include +\texttt{wx/wxprec.h} and then, inside \texttt{#ifndef WX\_PRECOMP}, individual +headers you need.} \twocolitem{\_UNICODE and UNICODE}{both are defined if wxUSE\_UNICODE is set to $1$} \twocolitem{wxUSE\_GUI}{this particular feature test macro is defined to $1$ when compiling or using the library with the GUI features activated, if it is @@ -174,4 +184,3 @@ don't include compiler flags needed for multithreaded code generation. This implies that wxUSE\_THREADS is $0$ and also that other (non wx-based) threading packages cannot be used neither.} \end{twocollist} -