🚀 go-pugleaf

Hi, 
On the Shared Library project that works, here are my access paths:
{Compiler}Mac OS Support
{Compiler}MSL/MSL_C
{Compiler}MSL/MSL_C++
{Compiler}MSL/MSL_Extras

And in the Shared Library project that DOESN'T work, here are the access
paths:
{Compiler}Mac OS Support
{Compiler}MSL/MSL_C
{Compiler}MSL/MSL_C++
{Compiler}MSL/MSL_Extras

What do I need to change?

Jaime
On 12/8/03 1:44 PM, in article
mwron-0C0D21.13445208122003@enews.newsguy.com, "MW Ron"
<mwron@metrowerks.com> wrote:

> In article <BBFA0A71.57DF%nvdeveloper@nvision-tech.com>,
> NV Developer <nvdeveloper@nvision-tech.com> wrote:
> 
>> Hi,
>> I have Codewarrior v9 for the Mac and I created a shared lib project using
>> the carbon libraries and the compiler keeps thinking that I am working with
>> Mac OS 8. I tried using a prefix file for the project but it is still using
>> the header file from the Universal Headers to get its definitions. Any ideas
>> on what could be missing here? Thanks in advance!
>> 
>> Jaime Rios
> 
> As you have discovered you were doing CFM programming.
> 
> I know the names of the linkers and tools could be better named, but
> I'll be darned if I can come up with better names.  The PEF/CFM carbon
> tools have had that name for a long time and the Mach-O ones have Mac OS
> X in the name.
> 
> The access paths will ultimately determine which headers are included,
> if you have Mac OS Support it will get the CFM Carbon headers if you
> have Mac OS X support it will get the OS X ones.
> 
> If I've just confused you please continue to ask questions.  It isn't
> hard to understand but I can see it could be confusing.
> 
> Ron