How to extend Xcode gcc to cross compile - or why does gcc..

vze35xda.DeleteThis@verizon.net (Jim Schimpf) writes:

 > I am very interested in this also. Did you change the target via
 > Rules tab of the Target <my target> Info window ? It seems to allow a
 > custom script to handle C source files. Haven't done anything myself
 > yet, waiting for someone smarter to try it :)

I come from a Linux environment and did once build GCC from source.
GCC will do cross-target compiling if the options have been compiled
in. You also need the appropriate libraries to link against, IIRC.
I only skimmed the details because I was not building a cross-compile
target at the time.

If you fetch the GCC sources from GNU, you can dig through the docs
and setup a cross compiler. You will be able to compile it with the
GCC that came with XCode. It is probably easier to do this all from
the command line.

I have GCC on a Debian box, so I'm not about to go to all that
trouble ;-). I'll just take my projects and rebuild them on that to
make sure the code will in fact build.

If an easier way to do this is found, let me know. I'm not using
XCode per se. I do plan to take advantage of the interface builder.
But my primary editor is Emacs and it is an IDE.

Good luck.

--
One Emacs to rule them all. One Emacs to find them,
One Emacs to take commands and to the keystrokes bind them,

All other programming languages wish they were Lisp.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: How to extend Xcode gcc to cross compile - or why does gcc.. 

 >
 > I am very interested in this also. Did you change the target via
 > Rules tab of the Target <my target> Info window ? It seems to allow a
 > custom script to handle C source files. Haven't done anything myself

I have not tried but seen this. It might work.

What I did also not find yet is any Tab to set the compiler version in
Xcode. Project Builder allowed to do so. It seems to be hard-coded
into Xcode based on the compatibility SDK that is selected (OS X 10.x
needs gcc-2.95.2).

 > yet, waiting for someone smarter to try it :)

In the meantime, I have used the older scheme that was already working
in Project Builder: a makefile that is added as an additional Build
Phase to the Target. The makefile uses all the settings to start the
cross-compiler and linker after building for MacOS X in the 'build'
directory.

The result is published as Zaurus-X-gcc-2.95.3X10.3a1 (please search
at MacUpdate or VersionTracker).

hns<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: How to extend Xcode gcc to cross compile - or why does gcc.. 

David Steuber <david.steuber.DeleteThis@verizon.net> wrote in message news:<m265gtuj9l.fsf.DeleteThis@david-steuber.com>...
 >
 > GCC will do cross-target compiling if the options have been compiled
 > in. You also need the appropriate libraries to link against, IIRC.

The cross-compiler backend and the libraries are already compiled and
available (Zaurs-X-gcc). The missing link is to put it under the
control of the 'gcc' command line driver that I hope is called by
Xcode.

This brings me to an other idea: I could try it vice versa - using the
cross-compiler front-end 'gcc' to call the darwin/ppc compilers if
specified by -b.

 > If an easier way to do this is found, let me know. I'm not using
 > XCode per se. I do plan to take advantage of the interface builder.

I think Interface Builder creates NIB-files that work only with Carbon
or Cocoa frameworks - which must be available/cross-compiled as well.
So I think it can't be used without Xcode at all.

hns<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: How to extend Xcode gcc to cross compile - or why does gcc.. 

hns DeleteThis @computer.org (Dr. Nikolaus Schaller) wrote in message news:<e5f20ec4.0312080639.56c5d6c6 DeleteThis @posting.google.com>...
  > >
  > > I am very interested in this also. Did you change the target via
  > > Rules tab of the Target <my target> Info window ? It seems to allow a
  > > custom script to handle C source files. Haven't done anything myself
 >
 > I have not tried but seen this. It might work.
 >
 > What I did also not find yet is any Tab to set the compiler version in
 > Xcode. Project Builder allowed to do so. It seems to be hard-coded
 > into Xcode based on the compatibility SDK that is selected (OS X 10.x
 > needs gcc-2.95.2).

Click the disclosure triangle for the Target (XCode) then pick your
target. Pick Get Info and
you will get a Target <your target Name> Info window. Then pick Rules
and under System C Rule you can Process <type of file> using <here you
pick which type of compiler 3.3,3.1.... or custom script.

 >
  > > yet, waiting for someone smarter to try it :)
 >
 > In the meantime, I have used the older scheme that was already working
 > in Project Builder: a makefile that is added as an additional Build
 > Phase to the Target. The makefile uses all the settings to start the
 > cross-compiler and linker after building for MacOS X in the 'build'
 > directory.
 >
 > The result is published as Zaurus-X-gcc-2.95.3X10.3a1 (please search
 > at MacUpdate or VersionTracker).

Thank you I will look at this.

 >
 > hns<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: How to extend Xcode gcc to cross compile - or why does gcc..