Re: #define when framework style includes are used?
Re: #define when framework style includes are used?
- Subject: Re: #define when framework style includes are used?
- From: "Glenn L. Austin" <email@hidden>
- Date: Fri, 7 Nov 2008 07:55:38 -0800
On Nov 7, 2008, at 7:38 AM, Thomas Engelmeier wrote:
On 07.11.2008, at 15:52, Sherm Pendley wrote:
On Nov 6, 2008, at 5:42 AM, Thomas Engelmeier wrote:
I'm working on an cross-platform project where all other platforms
use a non-framework variant of a library that is packaged up as
Framework on OS X. I'd really prefer to keep out contitional
compilation at all and leave the code as it is.
Is there an recommended way to add the framework include folder as
header search path, i.e.
{SDK_FOLDER}/System/Library/Frameworks/ThatFrameWork/Headers/?
Have you considered turning the question around? That is, instead
of trying to make "#include <foo.h>" work on the Mac, would it be
feasible for you to install headers on the other platforms in a
subdirectory, for example /usr/local/include/ThatFramework, so that
"#include <ThatFramework/foo.h>" works everywhere?
Nice idea, though I'm not sure if that's worth the effort in 300+
existing source files (plus corresponding headers).. That framework
typedefs some basic types.
...or you could have a "define" in your Mac project's preprocessor
macros (see GCC_PREPROCESSOR_DEFINITIONS).
Personally, while I *can* determine what platform I'm building for, I
prefer to have a #define that I can always depend upon because I
defined it.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden