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 / May 2005



Tip: Looking for answers? Try searching our database.

CW 8.3 and Tiger 10.4

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Lennart.Thelander@berga.nu - 17 May 2005 10:34 GMT
Hi.

After installing Mac OS 10.4, my mach-o apps will no longer compile
with CodeWarrior 8.3. "Can't read Dylib". I try to "BuildLibraries" (in
the MSL folder), but the file "ppc/ansi.h" is now missing (along with
others) so I get thousands of compile errors. What gives?

Buying CW 9 is not an option, since it's "unavailable" according to
Metrowerks site.

Regards
Lennart Thelander
Stephane Madrau - 17 May 2005 14:17 GMT
> After installing Mac OS 10.4, my mach-o apps will no longer compile
> with CodeWarrior 8.3. "Can't read Dylib". I try to "BuildLibraries"
> (in the MSL folder), but the file "ppc/ansi.h" is now missing (along
> with others) so I get thousands of compile errors. What gives?

I've successfully built my Mach-O apps on Tiger by setting the {OSX Volume}
path to point on the /10.2.8 SDK/ (as well as on the 10.3.0 SDK; but no more
on the 10.3.9, since this ones includes new type of dylibs that the CW8
linker cannot handle).
I have also switched from MSL libs to the BSD libs. I have built these on a
previous version (10.3.8 IIRC, I have not tried to rebuild them on 10.4).

In fact I had most of the difficuties when I installed 10.3.9. Then I needed
the above modifications. Afterwards, the upgrade to 10.4 went flawlessly.
It's possible that it depends on the frameworks that you use in your apps,
it's possible that some dylibs were updated before 10.3.9, but I personnaly
had no problems with 8.3 before.

The only thing that now doesn't work any more (in the IDE) is drag-and-drop
of files from the Finder in project windows.

Signature

Stéphane

trygveinda@gmail.com - 17 May 2005 22:27 GMT
How does one do this? I have 10.3.9 running on one system and 10.3.8 on
another. Will CW8.3 not work under 10.3.9?

I am using Dev Tools 1.5 and linking with mwcrt1.o

In XCode Tools I have MacOSX10.3.pkg and MacOSX10.2.8.pkg. What do
these do? I installed the standard install package from the Dev Tools
CD.

Thanks,

T.
Lennart.Thelander@berga.nu - 18 May 2005 08:30 GMT
> How does one do this? I have 10.3.9 running on one system and 10.3.8 on
> another. Will CW8.3 not work under 10.3.9?

Yes, CW 8.3 works fine under 10.3.9. It doesn't work under 10.4, not
even when using the 10.3.9 SDK. In fact the 10.2.8 SDK was worse than
the 10.3.9 SDK with more errors to fix.

/Lennart
Stephane Madrau - 18 May 2005 08:40 GMT
> It doesn't work under 10.4, not
> even when using the 10.3.9 SDK.

That's certainly false, depending on the projects you have.
It works fine on my config, with both the 10.2.8 or 10.3.0 SDK.

Signature

Stéphane

kiyookasan - 19 May 2005 00:30 GMT
I agree.  No trouble building either mach-o or CFM binaries on my new
Tiger install as long as using 10.2.8 SDK as the OSX Root.

Gen
Lennart.Thelander@berga.nu - 25 May 2005 07:55 GMT
Lennart.Thelan...@berga.nu wrote:
> It doesn't work under 10.4, not
> even when using the 10.3.9 SDK.

>That's certainly false, depending on the projects you have.
>It works fine on my config, with both the 10.2.8 or 10.3.0 SDK.

Clarification:
I can't build MetroWerks "BuildLibraries" under 10.4 or 10.4.1, even
when pointing to 10.3.9 SDK or 10.2.8 SDK. Using the 10.3.9 SDK it's
the PowerPlats that doesn't build. I'm not using PowerPlant, so I'm OK.
I never tried building my apps before building the libraries. It might
have worked.

/Lennart
Stephane Madrau - 25 May 2005 10:47 GMT
> I can't build MetroWerks "BuildLibraries" under 10.4 or 10.4.1, even
> when pointing to 10.3.9 SDK or 10.2.8 SDK.

I also think I encountered this problem. I can't remember what I did,
but I've been able to work around, with the 10.3.0 SDK. I just know had
to tweak for the MacHeaders (which at the end built fine with the 10.4.0
SDK), and also for the MSL libs.

> Using the 10.3.9 SDK it's
> the PowerPlats that doesn't build. I'm not using PowerPlant, so I'm OK.

I don't either. In all cases, I'm conscious it's just a temporary
solution, just to allow to continue working.

Signature

Stéphane

MW Ron - 26 May 2005 15:25 GMT
>> I can't build MetroWerks "BuildLibraries" under 10.4 or 10.4.1, even
>> when pointing to 10.3.9 SDK or 10.2.8 SDK.
[quoted text clipped - 9 lines]
>I don't either. In all cases, I'm conscious it's just a temporary
>solution, just to allow to continue working.

Here is the fix for 10.3  I assume you have to make similar fixes for
10.4

Ron

for 8.3 and 10.3...

Get the XCode Tools CD,  reinstall it, choose the optional packages  and
there is a 10.2.7 SDK  install that,  you can do this even after doing
the original installation.

In CodeWarrior 8.3  global Preferences...
change your Source Tree for OS X Volume
from
/
to
/Developers/SDKs/MacOSX10.2.7SDK/

If you want to stop here  you can if you have already updated to 8.3 on
10.2

But I recommend that you re-precompile the Mach-O  precompiled headers .  
Open the BuildMacOSXSupport.mcp
in
Metrowerks CodeWarrior 8.0
   /Metrowerks CodeWarrior
       /MSL/(MSL_Build_Projects)
           /OS X

and build all in that.  

But to rebuild the libraries...

Then... this is an unofficial and non-supported fix.  Since it involves
changing Apple's header

In Apple's Limits.h
in /Developers/SDKs/MacOSX10.2.7SDK/usr/include/ppc/limits.h

Change

#ifndef _PPC_LIMITS_H_
#define _PPC_LIMITS_H_

#define    CHAR_BIT    8        /* number of bits in a char */
#define    MB_LEN_MAX    6        /* Allow 31 bit UTF2 */

#define    CLK_TCK        100        /* ticks per second */

to

#ifndef _PPC_LIMITS_H_
#define _PPC_LIMITS_H_

#define    CLK_TCK        100        /* ticks per second */

#if !_MSL_USING_MW_C_HEADERS

#define    CHAR_BIT    8        /* number of bits in a char */
#define    MB_LEN_MAX    6        /* Allow 31 bit UTF2 */

At the end of the file add
#endif  /* _MSL_USING_MW_C_HEADERS */
before
#endif /* _PPC_LIMITS_H_ */

Rebuild the precompiled headers and rebuild the MSL Mac OS X libraries
Open the Build.MacOSX.mcp
in
Metrowerks CodeWarrior 8.0
   /Metrowerks CodeWarrior
       /MSL/(MSL_Build_Projects)
           /OS X

You should be OK

Signature

Metrowerks Community Forum is a free online resource for developers
to discuss CodeWarrior topics with other users and Metrowerks' staff
       --   http://www.metrowerks.com/community  --

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

Michael Wingfield - 20 May 2005 00:03 GMT
>>After installing Mac OS 10.4, my mach-o apps will no longer compile
>>with CodeWarrior 8.3. "Can't read Dylib". I try to "BuildLibraries"
[quoted text clipped - 16 lines]
> The only thing that now doesn't work any more (in the IDE) is drag-and-drop
> of files from the Finder in project windows.

Specifically what are the steps we need to do to point to /10.2.8 SDK/ ?

Thanks,
Mike
Stephane Madrau - 20 May 2005 08:04 GMT
> Specifically what are the steps we need to do to point to /10.2.8 SDK/ ?

First install the SDK from the Panther or Tiger install disc.

Then, in the CW IDE Preferences, change your Source Tree for {OS X
Volume} from "/" to "/Developer/SDK/MacOSX10.2.8SDK/"

Signature

Stéphane

Michael Wingfield - 21 May 2005 21:40 GMT
>> Specifically what are the steps we need to do to point to /10.2.8 SDK/ ?
>
> First install the SDK from the Panther or Tiger install disc.
>
> Then, in the CW IDE Preferences, change your Source Tree for {OS X
> Volume} from "/" to "/Developer/SDK/MacOSX10.2.8SDK/"

Bear with me on this one: I really need to get this to work.

Where is the SDK on the Panther install disc?
Do I need to reinstall something AFTER I installed Tiger?
I already have a /Developer folder but no SDK folder inside.

Thanks in advance,
Mike
Dave Seaman - 22 May 2005 00:07 GMT
>>> Specifically what are the steps we need to do to point to /10.2.8 SDK/ ?
>>
>> First install the SDK from the Panther or Tiger install disc.
>>
>> Then, in the CW IDE Preferences, change your Source Tree for {OS X
>> Volume} from "/" to "/Developer/SDK/MacOSX10.2.8SDK/"

> Bear with me on this one: I really need to get this to work.

> Where is the SDK on the Panther install disc?

It's not on the Panther install disc.  There is a "MacOSX10.2.pkg" on the
XCode Tools disk that comes with Panther, but the SDK that it installs is
10.2.7, not 10.2.8.  This is the one I used under Panther, and it worked
ok.

The Tiger DVD has a "MacOSX10.2.8.pkg", and this seems to be the
recommended version with Tiger.  It seems to be ok when using the IDE,
but I have not had any success in getting the command-line tools to work
under Tiger.  Even the minimal program

    int main() {}

yields an illegal instruction when I run it on a G4.

> Do I need to reinstall something AFTER I installed Tiger?
> I already have a /Developer folder but no SDK folder inside.

Install "XCode Tools/Packages/MacOSX10.2.8.pkg".
Don't forget to change your Source Tree as mentioned above.

Signature

Dave Seaman
Judge Yohn's mistakes revealed in Mumia Abu-Jamal ruling.
<http://www.commoncouragepress.com/index.cfm?action=book&bookid=228>

Michael Wingfield - 22 May 2005 16:57 GMT
Thanks Dave and Stephane for all your help.  I am back in business.
Aren't newsgroups wonderful?!

Mike

>>>>Specifically what are the steps we need to do to point to /10.2.8 SDK/ ?
>>>
[quoted text clipped - 26 lines]
> Install "XCode Tools/Packages/MacOSX10.2.8.pkg".
> Don't forget to change your Source Tree as mentioned above.
 
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



©2008 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.