Selecting alternative compiler via rules tab - compiler not listed
Selecting alternative compiler via rules tab - compiler not listed
- Subject: Selecting alternative compiler via rules tab - compiler not listed
- From: "J.M. Brough" <email@hidden>
- Date: Tue, 26 Jul 2005 18:13:39 +0100
Hi,
I've installed the arm-elf compiler and wish to use it with XCode.
Scanning the archives pulled out a message from Chris Espinosa
pointing out how easy it is. Unfortunately, the arm compiler does
not appear on the list.
During installation of the gcc compiler it states that it must reside
in /usr/local, as the path is hard coded. What this results in is
that you find gcc at the following path.
/usr/local/arm-elf/bin/
There are symlinks all prefixed arm-elf-xxx in /usr/local/bin so you
can type arm-elf-gcc and get the right compiler. As a result of
gcc_select and the PATHS var you can only invoke gcc by using the
full pathname. It works fine and I'm hoping that this won't cause
any major problems.
Doing a gcc -v gives the following output.
miami:/usr/local/arm-elf/bin jason$ /usr/local/arm-elf/bin/gcc -v
Reading specs from /usr/local/lib/gcc-lib/arm-elf/2.95.3/specs
gcc version 2.95.3 20010315 (release)(ColdFire patches - 20010318
from http://fiddes.net/coldfire/)(uClinux XIP and shared lib patches
from http://www.snapgear.com/)(MacOSX patches by email@hidden)
This version does not appear in the list given via the System C Rule
from the Rules tab. I don't want to use gcc_select (It doesn't show
up there either as an option) as this would affect other development
projects. I'd like to be able to inform XCode in some way so that it
appears on the System C Rules list. I'm running 10.4.2 and during
installtion of XCode 2.1 I chose to install all the compilers
available - they all appear as expected.
Failing this, if it requires the creation of a custom script then
point me in the write direction regarding the documentation. I
selected Custom Script and it asked about making a copy and I
agreed. I heard the drive access, but then nothing after that. What
exactly did it do and where did it do it??
The compiler is working correctly. I've been using BBEdit to write
code and invoke the compiler, etc. Since I wrote the program via
XCode in C as a regular command line tool and now are ready to port
it to the arm processor, it would be nice to carry on using XCode.
Although, working with only a main.c in BBedit with its ability to
access the command line to invoke gcc is so fast. I guess you can't
expect to gain all that functionality for free. :)
Thanks in advance.
Jason.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden