Re: PLATFORM DEFINE

On Tue, 18 Dec 2007 13:46:19 +0100, "Miky" <miky@xxxxxxxxxxxxxxxx>
wrote:

Hi All,



How do I know the platform define?

I'm not quite sure what you are asking. I'll try to provide info that
will answer, or at least be close.

If you are using the IDE that comes with one of the Microsoft
compilers, then when you choose a platform, the IDE chooses the
corresponding SDK and sets the macros appropriately. For eVC, you can
see these either of two ways:
1) Project -> Settings -> C/C++ -> Preprocessor -> Project Options
2) In Project -> Settings -> C/C++ -> Customize uncheck "Suppress
startup banner...", and then look at the first part of the compiler
output when you compile.

If you are using some other build system (perhaps nmake), then you
need to define the appropriate macros. Using one of the techniques I
just described will show you which macros you need to define. But at
least some are pretty easy to figure out from the header (.h) files.
For nmake, you can use -d arguments to define macros. If you need help
setting macros in another build environment, please ask so someone
_else_ can help (I probably won't know).




I have found in setup.h file on the wxwidget package these are define:



#if (_WIN32_WCE >= 400) && !defined(wxNO_RTTI)

#pragma comment(lib,"ccrtrtti.lib")

#endif

#if defined(__WINCE_STANDARDSDK__)

// DoDragDrop:

#pragma comment(lib,"olece400.lib")

#elif defined(__POCKETPC__)

// PocketPC build:

// DoDragDrop:

#pragma comment(lib,"ceshell.lib")

#pragma comment(lib,"aygshell.lib")

#elif defined(__HANDHELDPC__)

// Handheld PC builds. Maybe WindowsCE.NET 4.X needs another symbol.

#pragma comment(lib,"ceshell.lib")

#elif defined(__SMARTPHONE__)

// Smartphone build:

#pragma comment(lib,"ceshell.lib")

#pragma comment(lib,"aygshell.lib")

#else

#error "Unknown SDK, please fill-in missing pieces"

#endif



My SDK that I read on VS2005 is NAV53_v14 (ARMV4I).. What is the my define
name ?

Thanks

Miky


-----------------------------------------
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).

Robert E. Zaret, eMVP
PenFact, Inc.
20 Park Plaza, Suite 478
Boston, MA 02116
www.penfact.com
.

Relevant Pages

  • Re: Correspondence between headers and macros
    ... So Norcroft doesn't support "#pragma once". ... Supported by some, but not all compilers. ... CPP supports two more ways of indicating that a header file should ...
    (comp.lang.c)
  • Re: C is too old? opinions?
    ... You insisted that this pragma is supported by many compilers, ... I cannot find any mention of it in the documentation for my current gcc ... If they support if, it is undocumented and probably deprecated. ... OS platforms and all the mainstream compilers used this pragma I know I ...
    (comp.lang.c)
  • RE: pragma section
    ... The compilers available with eVC4.0 do not support that pragma. ... be using Windows CE 5.0 with Platform Builder or Visual Studio .NET 2005 ... > int j = 0; ...
    (microsoft.public.windowsce.app.development)
  • Re: Could C++ do this without the #pragma
    ... > more common version of Test Collector, and not need macros. ... > You misunderstand the pragma. ... but there is more to the use of these directives ... than reducing code size and compile times. ...
    (comp.lang.cpp)
  • Re: if !defined and #pragma once
    ... Microsoft added the #pragma once ... construct, but since code had to be compiled with older compilers, the older ... include-guards had to remain in place. ... Starting with VS.NET, this older support was dropped, and newer wizards only put in the ...
    (microsoft.public.vc.mfc)
Loading