🚀 go-pugleaf

In article <mwron-539349.17200324012002@enews.newsguy.com>, MW Ron
<mwron@metrowerks.com> writes
>
>
>Software Updates: CodeWarrior for Mac OS, Professional Edition, Release 
>7.2 Update is available at 
>http://www.metrowerks.com/download/

In folder "OS X Development Items", what are the files mwccppc and
mwldppc? What should I do with them?

Andy Robinson, Seventh String Software, www.seventhstring.demon.co.uk

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.

In article <jvRi0KAA3VU8EweX@seventhstring.demon.co.uk>,
 Andy Robinson <andy@seventhstring.demon.co.uk> wrote:

>In article <mwron-539349.17200324012002@enews.newsguy.com>, MW Ron
><mwron@metrowerks.com> writes
>>
>>
>>Software Updates: CodeWarrior for Mac OS, Professional Edition, Release 
>>7.2 Update is available at 
>>http://www.metrowerks.com/download/
>
>In folder "OS X Development Items", what are the files mwccppc and
>mwldppc? What should I do with them?

They are command line tools  mwcc for PowerPC and mwld for PowerPC and 
you should probably just let them be :)

Ron

-- 
       TOP PICK   HandHeld Computing - issue 4.5
   "The best overall development tool for the Palm OS"

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

Andy Robinson <andy@seventhstring.demon.co.uk> wrote:

> In article <mwron-539349.17200324012002@enews.newsguy.com>, MW Ron
> <mwron@metrowerks.com> writes
> >
> >
> >Software Updates: CodeWarrior for Mac OS, Professional Edition, Release
> >7.2 Update is available at 
> >http://www.metrowerks.com/download/
> 
> In folder "OS X Development Items", what are the files mwccppc and
> mwldppc? What should I do with them?

They are the Mac OS X command line versions of the compiler and linker
respectively.  On my machine, the original Pro 7 installation created a
"bin" folder in my user account home directory (i.e. ~/bin) and placed
them there.  You can simply copy them with Finder, replacing the old
versions.

(If you want to set up the compiler to be available for any user, you
might need to adjust their permissions as well as moving them to
somewhere like /usr/local/bin.)

-- 
David Empson
dempson@actrix.gen.nz

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

In article <1f6kx9b.1xg9xaz1ujl7x0N%brunobl@REMOVEifrance.com>,
 brunobl@REMOVEifrance.com (Bruno Blondeau) wrote:

>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?)

We are going to drop our MPW compilers with CW 8 and go to the 
commandline compilers for both PEF and Mach-O in OS X  I think this will 
be great for everyone.  Basically we are looking for a simple 
substitution for GCC in a Makefile.

>Are these command line compilers able to completly replace GCC? This
>would be a very good goal, since your compiler is generating better
>code.

I think so but I don't know how many quirks there will be.

I don't know about plugins for Project builder, but if you can use 
interface builder and do Cocoa from CodeWarrior then... We'll see.

Ron

>Or even being able to use them from ProjectBuilder, for Cocoa
>development purposes, as from my tests, your compiler is even able to
>compile Objective-C++ code (well, there are some small problems with
>some parts of the MSL. iostream uses reserved keywords such as in/out as
>variables).
>Unless you plan better cooperation between your IDE and Interface
>Builder, of course, which would be even better.
>

-- 
       TOP PICK   HandHeld Computing - issue 4.5
   "The best overall development tool for the Palm OS"

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