🚀 go-pugleaf

In article <1f6kx9b.1xg9xaz1ujl7x0N%brunobl@REMOVEifrance.com>,
Bruno Blondeau <brunobl@REMOVEifrance.com> wrote:
>Josef W. Wankerl <jwankerl@metrowerks.com> wrote:
>
>> In article <jvRi0KAA3VU8EweX@seventhstring.demon.co.uk>,
>>  Andy Robinson <andy@seventhstring.demon.co.uk> wrote:
>> 
>> > In folder "OS X Development Items", what are the files mwccppc and
>> > mwldppc? What should I do with them?
>> 
>> Those are the OS X command line compilers.  On your Pro 7 tools CD, 
>> there's a corresponding folder called OS X Development Items with a note
>> explaining the tools and how to install them.
>
>I never tried to use them, but I would be curious to know what your
>goals are with these compilers (what kind of use do you expect from your
>customers?)
>
>Are these command line compilers able to completly replace GCC? This
>would be a very good goal, since your compiler is generating better
>code.
>

Funny you should ask; I'm in the process of trying (for about the tenth time)
to get away from the IDE and use the cross-platform makefiles + autoconf that
works for other UNIX platforms.

Just to avoid duplicating my effort, here are some of the problems I ran into:

1) use the -gccinc flag to get "normal" include behavior (that is, include paths
are resolved relative to the including file.)  The default behavior (look relative
to the build directory) seems _crazy_ to me, because it totally breaks the abstraction
of packages you may choose to include.

2) Apple's include files don't seem to correctly anticipate the use of command-line
Metrowerks tools.  That is, if __MWERKS__ is defined, they include files like
MacroDefinitions.h (sp?) directly rather than supplying the needed relative path names.
The solution is to be sure to define __CF_USE_FRAMEWORK_INCLUDES__ in your command-line
calls to mwccppc

3) I still haven't figured out how to gracefully incorporate precompiled headers.

john