[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Portability/Compatability between GNUstep <---> Cocoa...

From: Kazunobu Kuriyama
Subject: Re: Portability/Compatability between GNUstep <---> Cocoa...
Date: Tue, 13 Jan 2004 08:15:07 +0900
User-agent: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.4) Gecko/20030624 Netscape/7.1

Alex Perez wrote:

Not sure what you are asking for. But if you only want to find out if
your code compiles in a GNUstep or a MacOSX environment a test for
#ifdef GNUSTEP should do.

This seems to be just the one I'm seeking for. Which file defines the
macro? Or is this
one defined by each programmer?

The problem with #ifdef GNUSTEP is that, AFAIR, it is still defined if you
use GNUstep-make to build under OS X. That's no good. Apple's GCC always
defines __APPLE__ and there's also MAC_OS_X (or is it MAC_OSX, I can never

Thank you for the information.

When an Apple machine has both GNUstep and Cocoa library, we can't use
__APPLE__ alone to distinguish these libraries one another.

Also, if I remember correctly, there were emails on this list which told
some people use GNUstep-make on Mac.  In this case, the predefined macro
GNUSTEP doesn't work for the distinction I need, i.e.,

   <GNUstep proper code comes here>
   <Cocoa proper code comes here>

Should we GNUsteppers rely on MAC_OS_X or MAC_OSX which is defined by
another party that is not under our control?   I don't like this idea
because of an obvious technical reason.

So, let me reiterate my assertion: We need a predefined macro in GSConfig.h
(or wherever appropriate) which is used for identifying GNUstep and telling
it from Cocoa.

Could anyone please explain why this idea is wrong?   It's a quite easy
task to define _GNUSTEP_, _GNUSTEP_MAJOR_, _GNUSTEP_MINOR_ or other sweets
in the header.

- Kazunobu Kuriyama

reply via email to

[Prev in Thread] Current Thread [Next in Thread]