Mac Forum / Programming / CodeWarrior / June 2004

If I build a project, close it and then re-open it, the first time I
try to run or build it, it links again even though nothing has
changed. After that while the project is open it only links if
something has changed. Is there a reasons for this or is this a bug?

I'm finally upgrading my copy of CW from 8.3 to 9 and then on to 9.2. Is
there anything I should beware of, make sure of, or otherwise be aware
of before going ahead?
Ta.

I've started having instances where the debugger takes all the
processor and I have to force quit CW.  I restart my machine and
things are ok for a couple of debugging sessions then I have to force
quit CW again.

Ron,
I think I've uncovered the debugger setting that was causing the debugger
(CW9, G5 DP 1.8) to hang-- or at least connected with causing the problem:
In the IDE Preferences, under Debugger "Display Settings", there's a

hi, my Carbon application to be uses the Navigation Services.  I found
that the NewDlgHookYDUPP, NewModalFilterYDUPP, and NewActivateYDUPP and
NewFileFilterYDUPP (YD = your data) are not available in Carbon.  Is
there any documentation that explains the changes I need to make to ...

I'm unable to use gdb with a dylib that only contains data and no code.
I'm building the dylib with Codewarrior 9.1 on Mac OS X 10.3.3.
Here's the source for the data library:
/* data.cpp */

hi everyone, my application that I am porting to Carbon has an MDEF.  I
found about half the information on how to do this.  I was wondering if
someone could point me in the direction of a tutorial on how to do this.

 I added some code that uses 'memcpy' to my app, and it isn't recognized
when I compile for Carbon.  It does compile for Mach-O however.  Any
suggestions?
Thanks

I've got an app that has a group of inter-related routines that "get
rolling" via a single call, and *MIGHT*, depending on runtime
conditions, "lock up" the machine for as long as 90 seconds as they
perform a complex task that needs to be accomplished (from the app's

   I just ported an app from Mac OSX 10.2.6 and CodeWarrior 8.3 to OSX
10.3.3 and CodeWarrior 9.2.  I spent all afternoon trying to fix one compile
problem, though.  I've fixed the proble, but I'm quite curious as towhy I
had it in the first place.

What are the option available to debug a Classic application using CW 9.2.
I have used the remote debugging sucessfully but it is really
sssssssssslllllllllllllooooooooooooooooooowwwwwwwwww?  It takes 1 minute 23
seconds for the debugger to appear from the start of debug.  Are the ...