However, if you use the flat headers, you should take a look at what
they are. From /Developer/Headers/FlatCarbon:
#include <CoreServices/CoreServices.h>
It's not really saving you much.
-Jon
On Sep 21, 2006, at 6:49 AM, Theodore H. Smith wrote:
Thanks :)
On 21 Sep 2006, at 12:39, Þór Sigurðsson wrote:
You have an option of:
CFMCarbon/CarbonCore/MacMemory.h
CFMCarbon/MacMemory.h
and FlatCarbon/MacMemory.h
Since they don't live in the root of the include tree, you'll have
to:
a) add the correct path to the build include path ( -I/where/
ever/... )
or
b) provide the correct #include:
#include <CFMCarbon/MacMemory.h>
or
#include
"/Developer/SDKs/MacOSX10.4u.sdk/Developer/Headers/CFMCarbon/
MacMemory.h"
/Þór
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of
Theodore H. Smith
Sent: 21. september 2006 11:25
To: REALbasic Plugins
Subject: Including MacMemory.h . Header madness.
Hi people,
I'm trying to replace including <Carbon/Carbon.h> with <MacMemory.h>
Only problem is, that Xcode can't find it :(
How do I get Xcode to know where MacMemory.h is? The funniest thing,
is that if I select the text MacMemory.h and press command-opt-D...
Xcode DOES find it. So I think Xcode is just being difficult on
purpose.
Anyhow, how do I tell Xcode what it already knows, which is where to
find MacMemory.h?
The reason I want to use MacMemory.h instead of Carbon... is that
I'm
not actually developing a Mac app you see. I'm developing a cross
platform app, and so I don't need all the junk Carbon provides, I
just want a few low level type defines, and the function defintion
for BlockMoveData most importantly.
I TRIED just declaring BlockMoveData myself and not needing
MacMemory.h even, but for some stupid reason, the compiler wouldn't
link it despite that I copy/pasted it out of the headers myself!!!
I've no idea but I think it's some kind of define/linker magic that
makes it refuse to link, unless I use MacMemory.h.
Also, Carbon.h creates all sorts of problems for my project. I
actually needed to alter some header files, because they were using
"u32" as code variable names within inlined code in the headers, and
I'd already defined u32 as a type. This now means that my plugin
can't compile on anyone else's Mac unless they too alter the
standard
(locked!) header files.
I hate these sort of header madnesses.
Can someone just tell me where to find MacMemory.h?
--
http://elfdata.com/plugin/
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
--
http://elfdata.com/plugin/
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
--
Jonathan Johnson
[EMAIL PROTECTED]
REAL Software, Inc.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
