Help with precompiled headers

Help with precompiled headers

Post by john » Sun, 21 Dec 2003 05:36:57


I'm using CW 8.3 on OS X 10.2.8. I'm trying to rebuild precompiled using the
projects:

Build.MacOSX.mcp
BuildLibraries.Mach-O.mcp
BuildMacOSXSupport.mcp

All of them are bombing

Getting errors that Carbon/Carbon.h cannot be found,

pthread.h cannot be found .

This is my first experience with code warrior

Please Help

Thanks,
John
 
 
 

Help with precompiled headers

Post by Miro Juris » Sun, 21 Dec 2003 05:50:05


Install Apple developer tools.

hth

meeroh

--
If this message helped you, consider buying an item
from my wish list: < http://www.yqcomputer.com/ ;

 
 
 

Help with precompiled headers

Post by john » Sun, 21 Dec 2003 06:13:57

Meeroh

Thanks, I will persue.

Is there a doc somewhere that explains what apple tools metrowerks needs? I
could not find it.

-J
 
 
 

Help with precompiled headers

Post by spammerspi » Sun, 28 Dec 2003 07:50:54

I had the same problems as John Alesse until I downloaded the Developer Tools
and the August 2002 gcc update off the ADC website. Now, it's reduced my
errors in the BuildLibraries from something like 19,000+ to just 165 but I'm
now getting an error that it can't restart the IDE because "the CWMacOSXUtil
bundle is missing or too old." Help!


*****************
This account doesn't accept email. Please reply via this forum as I will be
checking for responses here. Thanks.
 
 
 

Help with precompiled headers

Post by Moises Lej » Mon, 29 Dec 2003 17:13:35

In article < XXXX@XXXXX.COM >, MW Ron says...


I might have a similar problem...
I have already downloaded the Dec 202 Developer Tools,
plus the Aug 2003 GCC update. I am trying to compile
something like the simpleJavaLauncher example from
the Apple web site, to start up a JVM from within a C
app, and I cannot get it to compile.

Problem #1:
The example from Apple wants to use <sys/resource.h>
To get that to compile, I need to include <sys/time.h>,
and then I get a collision with a MW header file on
using std::clock_t.

Problem #2:
I commented out the code that needed <sys/resource.h>
(assuming a default stack size, just to get it to work).
The code from Apple also needs to use <pthread.h> -
and I cannot get it to compile cleanly, either :-(.
If I #include <pthread.h> first, I get errors like
t32_t already defined, pointing me to a MW header.
If I #Include <sys/types.h> first, then <pthread.h>
I get a collision in using std::clock_t in another
MW header file.

I've tried putting ${COMPILER}/MSL before and after
/usr/include in the access path settings, and neither
one worked... I am assuming it is "just" a matter of
getting the right access path sequence in... Anyone
know what I am doing wrong? :-)

Thank you!

Moises
 
 
 

Help with precompiled headers

Post by spammerspi » Mon, 29 Dec 2003 18:28:49

<< I had the same problems as John Alesse until I downloaded the Developer
Tools
and the August 2002 gcc update off the ADC website. Now, it's reduced my
errors in the BuildLibraries from something like 19,000+ to just 165 but I'm
now getting an error that it can't restart the IDE because "the CWMacOSXUtil
bundle is missing or too old." Help! >><BR><BR>

Okay, here's an update. Since I wasn't getting any answers, I thought I'd mess
around with the installation (on the assumption that it wasn't working now and
if I screwed it up further, I could just pave over and restart again). Anyway,
I reinstalled the 8.1 updater over the 8.3 updater *AND* the August 2002 gcc
updater (I'd originally installed 8.0, updated it step by step all the way to
8.3 and then installed the Developer Tools 2002 and August 2002 gcc update) and
lo and behold, suddenly the CW IDE started right up and compiled itself (using
the "Bring up to date" menu option--what's the difference between this and
"Make" anyway?) all the way through without so much as a single error. Of
course, I might've shot myself in the foot somewhere and it might not show up
until I try to write a little "hello, world" program or something more
complicated and try to execute it... Insights would be welcome as to why a
reinstallation of 8.1 over an 8.3 update suddenly made everything "just work"
and if I've paved over my foot in the process. Thanks in advance.
*****************
This account doesn't accept email. Please reply via this forum as I will be
checking for responses here. Thanks.
 
 
 

Help with precompiled headers

Post by Sean McBri » Wed, 31 Dec 2003 04:34:21

In article < XXXX@XXXXX.COM >,



Several Apple headers are not 'C++ safe', and so in C++ projects you
must include them like so:

extern "c" {
#include <blah.h>
}

Maybe that will help.
 
 
 

Help with precompiled headers

Post by Moises Lej » Fri, 02 Jan 2004 05:12:23

In article < XXXX@XXXXX.COM >, Sean McBride says...

It was a good thought - but it did not pan out :-(.
I tried putting <pthread.h> first in my source file,
within an extern "C" block - and I still get type
collisions (this time on int32_t ...).

Moises
 
 
 

Help with precompiled headers

Post by Sean McBri » Fri, 02 Jan 2004 07:10:37

In article < XXXX@XXXXX.COM >,



Hmmm, that's a C99 type... maybe toggle the C99 checkbox?
 
 
 

Help with precompiled headers

Post by Moises Lej » Sun, 04 Jan 2004 14:14:33

In article < XXXX@XXXXX.COM >, Sean McBride says...

Well - this did not help, either... But it looks like me
problem is more fundamental than the header file...
I am not trying to build a Mach-0 binary, but rather
a Carbon/CFM one - which seems to be a requirement for
an Acrobat plug-in. But - it seems that the pthread lib
is only available for Mach-0... So I guess I get to
go and read up on MP tasks ... :-)

Thanks for all the help!

Moises
 
 
 

Help with precompiled headers

Post by Sean McBri » Mon, 05 Jan 2004 05:25:36

In article < XXXX@XXXXX.COM >,



Ahhhh. yeah, that's a problem. You can also check the archives here on
how to call Mach-O APIs from CFM binaries. But MP threads are pretty
straightforward too.
 
 
 

Help with precompiled headers

Post by MW Ro » Wed, 07 Jan 2004 07:32:26

In article < XXXX@XXXXX.COM >,



It would not affect any files that were modified so it would not have
mattered that you did an 8.1 update, it however probably reset the OS
search paths so it now was looking in the right place (kind of a rebuild
desktop).

That is my guess.

Sorry I wasn't here for the past couple weeks to help sooner.

Ron

--

Metrowerks, maker of CodeWarrior - "Software Starts Here"
Ron Liechty - XXXX@XXXXX.COM - < http://www.yqcomputer.com/ >