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 / February 2004



Tip: Looking for answers? Try searching our database.

Installation errors of CodeWarrior 8.3 on Panther

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jean-Claude Jesior - 02 Feb 2004 12:12 GMT
I decided recently to re-install CodeWarrior 8.3 because I encountered
some problems in debugging on Mac OS 10.3.2.

Prior to the re-installation, I trashed the 'Metrowerks CodeWarrior 8.0'
folder, the 'Developer' folder as well as the 'Metrowerks' preferences
folder.

The CodeWarrior 8.0 'Easy Install' went without problem, as well as the
2 subsequent updates (CW 8.2 Update and CW 8.3 Update). The installer
offered then me a chance to rebuild the C-libraries. The
'BuildLibraries.mcp' project opened normally and I initiated a Make.
However, I got 660 errors and 6 warnings on compiling
'Build.MacOSPPC.mcp'. Most errors were related to strings like:
        undefined identifier 'wchar_t'.

This occured repeatedly on 2 different computers running on 10.3.2 and
with 2 different sets of original CodeWarrior 8 Tools CDs. Each time I
got the same errors while building 'Build.MacOSX.mcp'. Installing Xcode
Tools (+ its update) did not help as well as doing an installation on
Mac OS 10.2.8.

If I ignore the above mentioned errors and I run a carbon C-project,
CodeWarrior compiles the application just fine but prevent to debug with
the following alert at the bottom of the project window:
        'Loading debugging data for target "MyProject Carbon" '.

I wonder what might be the reason of all this because I previously
worked with CodeWarrior 8.3 during several months.

Please help.
MW Ron - 02 Feb 2004 17:11 GMT
In article
<jean-claude.jesior-57E810.13125602022004@trompette.imag.fr>,

>I decided recently to re-install CodeWarrior 8.3 because I encountered
>some problems in debugging on Mac OS 10.3.2.
[quoted text clipped - 8 lines]
>'BuildLibraries.mcp' project opened normally and I initiated a Make.
>However, I got 660 errors and 6 warnings on compiling

Right the SDK changed so the headers and libraries don't fit... here is
the solution.
Ron

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/

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

You should be OK

Signature

Metrowerks, maker of CodeWarrior   -  "Software Starts Here"  
Ron Liechty - MWRon@metrowerks.com - <http://www.metrowerks.com>

Micah Koch - 02 Feb 2004 20:02 GMT
> In article
> <jean-claude.jesior-57E810.13125602022004@trompette.imag.fr>,
[quoted text clipped - 15 lines]
> the solution.
> Ron

He also says he deleted the Developer folder.  So he needs to re-install
the Apple Developer Tools first if he hasn't already.
Micah
MW Ron - 02 Feb 2004 22:04 GMT
>> In article
>> <jean-claude.jesior-57E810.13125602022004@trompette.imag.fr>,
[quoted text clipped - 18 lines]
>He also says he deleted the Developer folder.  So he needs to re-install
>the Apple Developer Tools first if he hasn't already.

Slapping forehead.   I have my own user Developer folder I was just
thinking of that.   Thanks for pointing this out.  Theya re called XCode
Tools now for 10.3 .

Ron

Signature

Metrowerks, maker of CodeWarrior   -  "Software Starts Here"  
Ron Liechty - MWRon@metrowerks.com - <http://www.metrowerks.com>

Jean-Claude Jesior - 03 Feb 2004 07:46 GMT
> In article
> <jean-claude.jesior-57E810.13125602022004@trompette.imag.fr>,
[quoted text clipped - 19 lines]
> there is a 10.2.7 SDK  install that,  you can do this even after doing
> the original installation.

In the Packages folder of my Xcode Tools CD there is no 10.2.7 package.
There is however a 'MacOSX10.3.pkg'. Is this equivalent ?

> In CodeWarrior 8.3  global Preferences...
>  change your Source Tree for OS X Volume
[quoted text clipped - 37 lines]
>
> Rebuild the precompiled headers

How can I rebuild the precompiled headers ?

> and rebuild the MSL Mac OS X libraries

I suppose that I must open the BuildLibraries.mcp file and initiate a
Make ?

> You should be OK

Thank-you for the help.

Jean-Claude Jesior
MW Ron - 03 Feb 2004 17:30 GMT
In article
<jean-claude.jesior-1647EC.08464703022004@trompette.imag.fr>,


>> 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 the Packages folder of my Xcode Tools CD there is no 10.2.7 package.
>There is however a 'MacOSX10.3.pkg'. Is this equivalent ?

Run it and there is an options that you can select and one of the
options is the 10.2.7 SDK

>> Rebuild the precompiled headers
>
>How can I rebuild the precompiled headers ?

When you finish updating 8.3  it will ask you if you want to do this. It
will rebuild all the precompiled headers then build the libraries for
you by opening the MSL Build Libraries project.

>> and rebuild the MSL Mac OS X libraries
>
>I suppose that I must open the BuildLibraries.mcp file and initiate a
>Make ?

CW 8.3 does this,  so be sure to make the changes suggested to the
headers before you run the build libraries project.

Ron

Signature

Metrowerks, maker of CodeWarrior   -  "Software Starts Here"  
Ron Liechty - MWRon@metrowerks.com - <http://www.metrowerks.com>

Jean-Claude Jesior - 04 Feb 2004 11:56 GMT
Ron, thank you so much for the help. I finally got CodeWarrior 8.3
successfully re-installed. For your records, there is no '10.2.7 SDK'
option in the Xcode Tools CD of Panther. Instead I have used the
Cross-Development/Mac OS X 10.2 SDK option.
For the newbies like me, I noted exactly what I did. This might help
some of us.

INSTALLING CODEWARRIOR 8.3 ON PANTHER 10.3.2

"Right the SDK changed so the headers and libraries don't fit... here is
the solution."
Ron

1- Start from scratch if you had CodeWarrior already installed:
a/ Trash the 'Developer' folder found at the root of your disk
b/ Trash the previously installed 'Metrowerks CodeWarrior 8.0' folder
found in the system 'Applications' folder
c/ Trash the 'Metrowerks' folder found in the system Library/Preferences
folder.

2- Install the December 2002 Developer Tools SDK
In order to download this SDK you must register (it's free) as an ADC
member on:
http://connect.apple.com/
Once on the Member Site, select 'Dowload Software', then 'Mac OS X',
then 'December 2002 Mac OS X Developer Tools'. Its size is 301.2 MB.
Once downloaded, unpack and install the SDK. This will create a
'Developer' folder at the root of your disk.

3- Install Xcode Tools using the 'Xcode Tools' CD that came with Panther.
Once you've selected the disk on which the installation should take
place, click on the 'Customize' button, and in 'Cross-Development'
select 'Mac OS X 10.2 SDK' (not 10.3 !). Upgrade.
This install modifies the 'Developer' folder where it creates a
'MacOSX10.2.7.sdk' folder.

4- Modify Apple's 'limits.h' found in
/Developer/SDKs/MacOSX10.2.7SDK/usr/include/ppc/limits.h
(modification provided by MW Ron):

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

And, at the end of the file, add :

#endif  /* _MSL_USING_MW_C_HEADERS */

before

#endif /* _PPC_LIMITS_H_ */

5- Install CodeWarrior 8.0 using the CD
Open the menu Edit > Preferences..., select 'Source Trees', select 'OS X
Volume' and change the 'Absolute Path' by Choosing
/Developer/SDKs/MacOSX10.2.7SDK/.

6- Install the CodeWarrior 8.2 and 8.3 updates
CodeWarrior Development Tools For Mac OS, v8.2 Update (21 MB):
ftp://ftp5.metrowerks.com/pub/updates/CWMacOS8/CW8_2_Update_Installer.sit
CodeWarrior Development Tools For Mac OS, v8.3 Update (28 MB):
ftp://ftp5.metrowerks.com/pub/updates/CWMacOS8/CW_8_3_Update_Installer.si
t
At the end of the 8.3 update the installer offers you to 'Open Build
Libraries'. This will automatically open 'BuildLibraries.mcp' for
rebuilding (select menu item Project > Make). The precompiled headers as
well as the MSL Mac OS X libraries will be rebuilt.

You are done.
MW Ron - 04 Feb 2004 18:41 GMT
In article
<jean-claude.jesior-4E0303.12562504022004@trompette.imag.fr>,

>Ron, thank you so much for the help. I finally got CodeWarrior 8.3
>successfully re-installed. For your records, there is no '10.2.7 SDK'
[quoted text clipped - 4 lines]
>
>INSTALLING CODEWARRIOR 8.3 ON PANTHER 10.3.2

-- % snip % --

This step is not necessary

>2- Install the December 2002 Developer Tools SDK
>In order to download this SDK you must register (it's free) as an ADC
[quoted text clipped - 4 lines]
>Once downloaded, unpack and install the SDK. This will create a
>'Developer' folder at the root of your disk.

You need to install the XCode Developer tools (they just renamed the
Developers tools)   You need the XCode for the latest GNU Debugger
anyway.

Ron

Signature

Metrowerks, maker of CodeWarrior   -  "Software Starts Here"  
Ron Liechty - MWRon@metrowerks.com - <http://www.metrowerks.com>

Jean-Claude Jesior - 12 Feb 2004 11:54 GMT
> In article
> <jean-claude.jesior-4E0303.12562504022004@trompette.imag.fr>,
[quoted text clipped - 26 lines]
>
> Ron

Ron, just to be sure that I'm not the only one to whom this happens:
After having done a proper CodeWarrior 8.3 installation in Mac OS 10.3.2,

If I open CodeWarrior in Classic mode, I'm able to :
  - debug Classic apps
  - run (but not debug) Carbon apps.
If I open CodeWarrior in Carbon mode, I'm able to :
  - run (but not debug) Classic apps
  - debug Carbon apps.

Debugging Classic apps in Carbon mode results in a spinning wheel which
necessitates a 'Force Quit' of CodeWarrior.
Is this correct ?
MW Ron - 12 Feb 2004 14:27 GMT
In article
<jean-claude.jesior-93EC2C.12542512022004@trompette.imag.fr>,

>Ron, just to be sure that I'm not the only one to whom this happens:
>After having done a proper CodeWarrior 8.3 installation in Mac OS 10.3.2,
[quoted text clipped - 5 lines]
>   - run (but not debug) Classic apps
>   - debug Carbon apps.

I'm not sure you can run classic apps from the IDE in OS X  mode, but I
never tried.  

>Debugging Classic apps in Carbon mode results in a spinning wheel which
>necessitates a 'Force Quit' of CodeWarrior.
>Is this correct ?

Yes.  One trick is to keep a second copy of CodeWarrior IDE that is
Classic Only so you don't have to make changes in Finder every time.  It
depends on how much classic debugging you do.

Ron

Signature

Metrowerks, maker of CodeWarrior   -  "Software Starts Here"  
Ron Liechty - MWRon@metrowerks.com - <http://www.metrowerks.com>

Jean-Claude Jesior - 24 Feb 2004 09:21 GMT
> In article
> <jean-claude.jesior-93EC2C.12542512022004@trompette.imag.fr>,
[quoted text clipped - 21 lines]
>
> Ron

I have used your trick of installing a second copy of CodeWarrior
dedicated only to Classic and it's neat.
However it happens from time to time that I inadvertendly debug a
Classic project in a 'Carbon' CodeWarrior (with a Cmd-R instead of
Cmd-Opt-R). I get then the spinning wheel which obliges me to do a
'Force Quit' destroying at the same time the unsaved modifications that
I could have done on other open projects.
I'm dreaming of a few lines of compiler directives which would be placed
at the very beginning of the program and which would tell CodeWarrior
NOT to debug in such a case but to simply run the Classic project.
(As a matter of fact, CodeWarrior is programmed to do so if a Carbon
project is debugged in a Classic mode ! It is not programmed to do so if
a Classic project is debugged in the Carbon mode).
Has someone an idea of where I could find this code ?

Jean-Claude Jesior
Tim - 26 Feb 2004 21:15 GMT
> 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
[quoted text clipped - 14 lines]
>
> Change

FYI, in latest XCode Tools that came with my G5, OSX 10.3.2, there is
no 10.2.7SDK, but there is a 10.2.8SDK (under Cross-Development
options).  Setting it as the Source Tree allowed the libraries to
build.  No change to limits.h was required.

Now, I haven't actually built anything else yet, but things seem okay.
Thanks for great help here.
 
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.