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



Tip: Looking for answers? Try searching our database.

CW 9.2 Slow linking after rebuilding pre-compiled headers

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
bluehaze - 29 Jun 2004 14:46 GMT
I'm using Codewarrior 9.2 and rebuilt the precompiled headers so I can use
some 10.3 specific Cocoa calls, and since I did that, linking has gone
from being nearly instantaneus to taking 1-2 minutes every time I
recompile.  Following the same instructions to rebuild precompiled headers
on another machine didn't result in this slow down.

Is there anything I can do to improve the linking speed?

Thanks!

Here's the instructions I followed:

From http://developer.apple.com/qa/qa2001/qa1316.html

1) If you were using precompiled headers for your CodeWarrior Mach-O
project, MacHeadersMach-O.h as your Prefix File in the C/C++ Language
Settings panel for example, you can rebuild them by following these
steps:
    1.      Navigate to your Metrowerks CodeWarrior directory.
    2.      Find the Build.MacOSX.mcp project located in
MSL/(MSL_Build_Projects)/OS X/.
    3.      Double click to open the Build.MacOSX.mcp project.
    4.      Select Make (Command+M) from the Project menu.
MW Ron - 29 Jun 2004 17:30 GMT
In article
<804979f7e9dfb5f8f6437e2e4294c64e@localhost.talkaboutmac.com>,

>I'm using Codewarrior 9.2 and rebuilt the precompiled headers so I can use
>some 10.3 specific Cocoa calls, and since I did that, linking has gone
[quoted text clipped - 3 lines]
>
>Is there anything I can do to improve the linking speed?

Make sure you are using the right thing.  You might want to use a
precompiled header directly  (++ for C++) so there isn't a check for
every file to see if it is C or C++ Linkage.  

Check the access paths and make sure you don't have any large recursive
search paths to start the list.  

Also do you have your caches on and is the computer time correct.

Ron

>Here's the instructions I followed:
>
[quoted text clipped - 9 lines]
>    3.      Double click to open the Build.MacOSX.mcp project.
>    4.      Select Make (Command+M) from the Project menu.

Signature

 Metrowerks, one of the world¹s top 100 companies and influencers
    in the software development industry. - SD Times  May 2004
              http://www.sdtimes.com/2004sdt100.htm
     
                 Metrowerks, maker of CodeWarrior
Ron Liechty - MWRon@metrowerks.com - http://www.metrowerks.com

bluehaze - 29 Jun 2004 19:02 GMT
Thanks for the quick response.  The problem was in my 'Access Paths'.  I
had an entry that contained '../..', removed it and that seemed to have
fixed my problem.
 
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.