Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Programming / CodeWarrior / December 2003



Tip: Looking for answers? Try searching our database.

Compile errors using 8.3, Mach-O, newer builds of OS X

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Mike G - 23 Dec 2003 16:16 GMT
Hi,

We use the MSL Mach-O headers in our 8.3 project.  The problem that
we're running into is that the Mach-O headers are build based off of
the MacOS Support folder in the Metrowerks folder.  That locks us to
the APIs in that folder.  It seems to me that the MacHeadersCarbon
project for building the headers should be using the
System:Library:Frameworks folder to get its APIs.

How do I correct this problem?  I can't just include Carbon/Carbon.h
because I then get build errors in MSL about having the non-MSL C
header file access path before the MSL access path.

Am I just including the wrong PCH (MSL MacHeadersMach-O.h) or is the
project to build the PCH wrong in including the MacOS Support folder?

Thanks,
-Mike
Thorrsten Froehlich - 24 Dec 2003 11:07 GMT
> Hi,
>
[quoted text clipped - 11 lines]
> Am I just including the wrong PCH (MSL MacHeadersMach-O.h) or is the
> project to build the PCH wrong in including the MacOS Support folder?

See the reply in your "Problems rebuilding MSL libraries under
Panther" thread. I guess it is the same problem.

   Thorsten
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.