Re: [CMake] #1f/#endif trouble...

2009-08-17 Thread ML
Hi Sean, It would seem to me that #if TARGET_OS_MAC #endif is not getting executed in my code. I have: #if TARGET_OS_MAC typedef unsigned char UInt8; typedef signed char S

Re: [CMake] #1f/#endif trouble...

2009-08-17 Thread Sean McBride
On 8/16/09 2:27 PM, ML said: >I am continuing my quest moving from XCode to CMake/Make > >This may be a Make specific question though. > >It would seem to me that > >#if TARGET_OS_MAC > >#endif > >is not getting executed in my code. > >I have: > >#if TARGET_OS_MAC > typedef unsigned char

Re: [CMake] #1f/#endif trouble...

2009-08-16 Thread Hendrik Sattler
Am Sonntag 16 August 2009 23:27:54 schrieb ML: > I have: > > #if TARGET_OS_MAC > typedef unsigned char > UInt8; > typedef signed char > SInt8; > typedef unsigned short

Re: [CMake] #1f/#endif trouble...

2009-08-16 Thread ML
Hi Mike, Yes, __APPLE__ is the preferred marker to decide if you are compiling on OS X. So was #if TARGET_OS_MAC OS 9? I know there are a lot of these and I dont care about OS 9 support any longer and I am already removing Metrowerks Support too. -Jason __

Re: [CMake] #1f/#endif trouble...

2009-08-16 Thread Mike Jackson
Yes, __APPLE__ is the preferred marker to decide if you are compiling on OS X. It is used in exactly the type of code that you presented. CMake, VTK, ITK, ParaView all use this construct. As far as I know Apple's GCC predefines it so you will not see it on the command line. I know it works because

[CMake] #1f/#endif trouble...

2009-08-16 Thread ML
Hi All, I am continuing my quest moving from XCode to CMake/Make This may be a Make specific question though. It would seem to me that #if TARGET_OS_MAC #endif is not getting executed in my code. I have: #if TARGET_OS_MAC typedef unsigned char