With the kind help of this forum I managed to compile a Carbon project
with CW 8.3 under Tiger. Unfortunately there are some functions that I
need and that are available not before Panther.
Is there a chance to import or bind these functions (some Core Graphics
stuff) at run time, or is there any other "trick"? Like using SDK
10.3.x instead of 10.2.8?
Ron L - 14 Oct 2005 17:48 GMT
>With the kind help of this forum I managed to compile a Carbon project
>with CW 8.3 under Tiger. Unfortunately there are some functions that I
[quoted text clipped - 3 lines]
>stuff) at run time, or is there any other "trick"? Like using SDK
>10.3.x instead of 10.2.8?
Wait for CW 10 and you should be OK.
Ron

Signature
CodeWarrior Community Forum is a free online resource for developers
to discuss CodeWarrior topics with other users and our staff
-- http://www.codewarrior.com/community --
Ron Liechty - ron.liechty@freescale.com - http://www.codewarrior.com
Chris Hanson - 15 Oct 2005 23:53 GMT
> With the kind help of this forum I managed to compile a Carbon project
> with CW 8.3 under Tiger. Unfortunately there are some functions that I
[quoted text clipped - 3 lines]
> stuff) at run time, or is there any other "trick"? Like using SDK
> 10.3.x instead of 10.2.8?
With Xcode, you would set your project's SDK to 10.3.9 and you would
set its Mac OS X Deployment Target build setting to 10.2. This way all
10.3.9 APIs would be available to your software but anything not
available on 10.2 would be weak-linked so you can still load and run on
10.2 as long as you don't call unavailable APIs.
You can achieve similar results using the MAC_OS_X_VERSION_MIN_REQUIRED
and MAC_OS_X_VERSION_MAX_ALLOWED preprocessor macros. See
<AvailabilityMacros.h> for details on them.
I don't know how any of this interacts with CodeWarrior, though.
-- Chris
Andreas.Kromke.nospam@gmx.de - 17 Oct 2005 09:34 GMT
Unfortunately XCode is no option, because its compiler cannot compile
the inline assembler. And CW 10 is no option because I definitely am
not going to spend any money on this.
Alexander Dymerets - 17 Oct 2005 19:44 GMT
> Unfortunately XCode is no option, because its compiler cannot compile
> the inline assembler.
It can.
http://developer.apple.com/documentation/DeveloperTools/Conceptual/MovingProject
sToXcode/migration_differences/chapter_2_section_14.html
Andreas.Kromke.nospam@gmx.de - 19 Oct 2005 14:19 GMT
Alexander Dymerets schrieb:
> It can.
No, gcc's inline assembler is not powerful enough, it does not compile
any CW inline code. Unfortunately I could not change my inline code to
be compileable with gcc. I think it has something to do with more than
one asm statement on a line, but I cannot remember completely.
And: The MacMAME code (http://www.macmame.org/) also does not
completely compile with XCode 2.1. I tried it, and Apple's compiler
just failed.
Some time ago I also tried to convert inline assembler to pure
assembler, but this was horrible, and I finally gave up, because the
assembler support in XCode was really bad.