🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.sys.mac.programmer.codewarrior
12 messages
12 total messages Started by NV Developer Mon, 08 Dec 2003 16:01
Why does Codewarrior want to compile for Mac OS 8?
#628
Author: NV Developer
Date: Mon, 08 Dec 2003 16:01
38 lines
2296 bytes
> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3153726070_19473345
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit

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

--B_3153726070_19473345
Content-type: text/html; charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Why does Codewarrior want to compile for Mac OS 8?</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana"><SPAN STYLE=3D'font-size:12.0px'>Hi,<BR>
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!<BR>
<BR>
Jaime Rios</SPAN></FONT>
</BODY>
</HTML>


--B_3153726070_19473345--
Re: Why does Codewarrior want to compile for Mac OS 8?
#629
Author: Frederick Cheung
Date: Mon, 08 Dec 2003 16:33
13 lines
1585 bytes
On Mon, 8 Dec 2003, NV Developer 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!

if your project is CFM then the Universal headers are the right ones to
use. If not, then did you create your project as a Mach-O project?

Fred
Re: Why does Codewarrior want to compile for Mac OS 8?
#630
Author: NV Developer
Date: Mon, 08 Dec 2003 16:35
14 lines
1565 bytes
I created an empty project and I set the PPC Target as "Shared Library".
This project is identical to another one I did and the older one doesn't
have any problems.

Jaime Rios

On 12/8/03 11:33 AM, in article
Pine.LNX.4.44.0312081632340.4429-100000@kern.srcf.societies.cam.ac.uk,
"Frederick Cheung" <fglc2@srcf.DUH.ucam.org> wrote:

> if your project is CFM then the Universal headers are the right ones to
> use. If not, then did you create your project as a Mach-O project?
> 
> Fred
Re: Why does Codewarrior want to compile for Mac OS 8?
#631
Author: Frederick Cheung
Date: Mon, 08 Dec 2003 16:58
25 lines
1996 bytes
On Mon, 8 Dec 2003, NV Developer wrote:

> I created an empty project and I set the PPC Target as "Shared Library".
> This project is identical to another one I did and the older one doesn't
> have any problems.

That sounds distinctly like a CFM project to me (for starters, i have PPC
Mac OS X Target). What linker are you using?

Fred

>
> Jaime Rios
>
> On 12/8/03 11:33 AM, in article
> Pine.LNX.4.44.0312081632340.4429-100000@kern.srcf.societies.cam.ac.uk,
> "Frederick Cheung" <fglc2@srcf.DUH.ucam.org> wrote:
>
> > if your project is CFM then the Universal headers are the right ones to
> > use. If not, then did you create your project as a Mach-O project?
> >
> > Fred
>
>
>
Re: Why does Codewarrior want to compile for Mac OS 8?
#632
Author: NV Developer
Date: Mon, 08 Dec 2003 17:38
33 lines
2113 bytes
PPC linker.

Jaime
On 12/8/03 11:58 AM, in article
Pine.LNX.4.44.0312081656420.4429-100000@kern.srcf.societies.cam.ac.uk,
"Frederick Cheung" <fglc2@srcf.DUH.ucam.org> wrote:

> On Mon, 8 Dec 2003, NV Developer wrote:
> 
>> I created an empty project and I set the PPC Target as "Shared Library".
>> This project is identical to another one I did and the older one doesn't
>> have any problems.
> 
> That sounds distinctly like a CFM project to me (for starters, i have PPC
> Mac OS X Target). What linker are you using?
> 
> Fred
> 
>> 
>> Jaime Rios
>> 
>> On 12/8/03 11:33 AM, in article
>> Pine.LNX.4.44.0312081632340.4429-100000@kern.srcf.societies.cam.ac.uk,
>> "Frederick Cheung" <fglc2@srcf.DUH.ucam.org> wrote:
>> 
>>> if your project is CFM then the Universal headers are the right ones to
>>> use. If not, then did you create your project as a Mach-O project?
>>> 
>>> Fred
>> 
>> 
>> 
> 
Re: Why does Codewarrior want to compile for Mac OS 8?
#633
Author: Frederick Cheung
Date: Mon, 08 Dec 2003 18:14
42 lines
2768 bytes
On Mon, 8 Dec 2003, NV Developer wrote:

> PPC linker.
>
Then your project is a CFM project.
You need Mac OS X PowerPC Mach-O

Fred
> Jaime
> On 12/8/03 11:58 AM, in article
> Pine.LNX.4.44.0312081656420.4429-100000@kern.srcf.societies.cam.ac.uk,
> "Frederick Cheung" <fglc2@srcf.DUH.ucam.org> wrote:
>
> > On Mon, 8 Dec 2003, NV Developer wrote:
> >
> >> I created an empty project and I set the PPC Target as "Shared Library".
> >> This project is identical to another one I did and the older one doesn't
> >> have any problems.
> >
> > That sounds distinctly like a CFM project to me (for starters, i have PPC
> > Mac OS X Target). What linker are you using?
> >
> > Fred
> >
> >>
> >> Jaime Rios
> >>
> >> On 12/8/03 11:33 AM, in article
> >> Pine.LNX.4.44.0312081632340.4429-100000@kern.srcf.societies.cam.ac.uk,
> >> "Frederick Cheung" <fglc2@srcf.DUH.ucam.org> wrote:
> >>
> >>> if your project is CFM then the Universal headers are the right ones to
> >>> use. If not, then did you create your project as a Mach-O project?
> >>>
> >>> Fred
> >>
> >>
> >>
> >
>
>
>
Re: Why does Codewarrior want to compile for Mac OS 8?
#634
Author: MW Ron
Date: Mon, 08 Dec 2003 18:44
36 lines
2650 bytes
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

-- 
                                 New from Metrowerks
 The CodeWarrior Wireless Development Kit for Symbian OS, SEMC P900 Edition
    Easy-to-use, integrated tools and hardware for SEMC P900 Development
http://www.metrowerks.com/MW/Develop/Wireless/Symbian/SymbianWDKC.htm

Ron Liechty - MWRon@metrowerks.com - http://www.metrowerks.com
Ron Liechty - MWRon@metrowerks.com - http://www.metrowerks.com
Re: Why does Codewarrior want to compile for Mac OS 8?
#635
Author: NV Developer
Date: Mon, 08 Dec 2003 19:17
48 lines
2726 bytes
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
Re: Why does Codewarrior want to compile for Mac OS 8?
#636
Author: MW Ron
Date: Mon, 08 Dec 2003 20:24
75 lines
3892 bytes
In article <BBFA386E.5935%nvdeveloper@nvision-tech.com>,
 NV Developer <nvdeveloper@nvision-tech.com> wrote:

>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

This is the correct path for CFM/PEF (classic Carbon) support.


>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


if you want to do Mach-0  you need the Mac OS X Support folder you need 
the /usr/lib  and /usr/include and the frameworks added, (Look at a 
Mach-O Stationery).

By the way if you are doing Carbon and want it to run on OS 8/9 and OS X 
be sure you have the right Carbon Resource and plist for it.

Ron

>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
>
>

-- 
                                 New from Metrowerks
 The CodeWarrior Wireless Development Kit for Symbian OS, SEMC P900 Edition
    Easy-to-use, integrated tools and hardware for SEMC P900 Development
http://www.metrowerks.com/MW/Develop/Wireless/Symbian/SymbianWDKC.htm

Ron Liechty - MWRon@metrowerks.com - http://www.metrowerks.com
Ron Liechty - MWRon@metrowerks.com - http://www.metrowerks.com
Re: Why does Codewarrior want to compile for Mac OS 8?
#638
Author: NV Developer
Date: Tue, 09 Dec 2003 19:20
74 lines
3757 bytes
Where is the plist located for the project?


On 12/8/03 3:24 PM, in article
mwron-0AAADF.15244208122003@enews.newsguy.com, "MW Ron"
<mwron@metrowerks.com> wrote:

> In article <BBFA386E.5935%nvdeveloper@nvision-tech.com>,
> NV Developer <nvdeveloper@nvision-tech.com> wrote:
> 
>> 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
> 
> This is the correct path for CFM/PEF (classic Carbon) support.
> 
> 
>> 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
> 
> 
> if you want to do Mach-0  you need the Mac OS X Support folder you need
> the /usr/lib  and /usr/include and the frameworks added, (Look at a
> Mach-O Stationery).
> 
> By the way if you are doing Carbon and want it to run on OS 8/9 and OS X
> be sure you have the right Carbon Resource and plist for it.
> 
> Ron
> 
>> 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
>> 
>> 
Re: Why does Codewarrior want to compile for Mac OS 8?
#603
Author: Sean McBride
Date: Tue, 09 Dec 2003 23:37
10 lines
1600 bytes
In article <BBFA0A71.57DF%nvdeveloper@nvision-tech.com>,
 NV Developer <nvdeveloper@nvision-tech.com> wrote:

> 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!

Create a new Mach-O based project.
Re: Why does Codewarrior want to compile for Mac OS 8?
#604
Author: MW Ron
Date: Wed, 10 Dec 2003 18:37
94 lines
4423 bytes
In article <BBFB8A94.5A8F%nvdeveloper@nvision-tech.com>,
 NV Developer <nvdeveloper@nvision-tech.com> wrote:

>Where is the plist located for the project?

You should have a .plc file for the project.

Ron


>On 12/8/03 3:24 PM, in article
>mwron-0AAADF.15244208122003@enews.newsguy.com, "MW Ron"
><mwron@metrowerks.com> wrote:
>
>> In article <BBFA386E.5935%nvdeveloper@nvision-tech.com>,
>> NV Developer <nvdeveloper@nvision-tech.com> wrote:
>> 
>>> 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
>> 
>> This is the correct path for CFM/PEF (classic Carbon) support.
>> 
>> 
>>> 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
>> 
>> 
>> if you want to do Mach-0  you need the Mac OS X Support folder you need
>> the /usr/lib  and /usr/include and the frameworks added, (Look at a
>> Mach-O Stationery).
>> 
>> By the way if you are doing Carbon and want it to run on OS 8/9 and OS X
>> be sure you have the right Carbon Resource and plist for it.
>> 
>> Ron
>> 
>>> 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
>>> 
>>> 
>
>

-- 
                                 New from Metrowerks
 The CodeWarrior Wireless Development Kit for Symbian OS, SEMC P900 Edition
    Easy-to-use, integrated tools and hardware for SEMC P900 Development
http://www.metrowerks.com/MW/Develop/Wireless/Symbian/SymbianWDKC.htm

Ron Liechty - MWRon@metrowerks.com - http://www.metrowerks.com
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads