Re: Help with custom build rule
Re: Help with custom build rule
- Subject: Re: Help with custom build rule
- From: Chris Espinosa <email@hidden>
- Date: Wed, 27 Jul 2005 22:25:34 -0700
On Jul 27, 2005, at 6:18 PM, Brant Sears wrote:
I'm using XCode 1.5. What is the easist way to create a custom build rule for my target for C source files that will have the effect of calling:
<my path>/gcc-3.3
instead of:
/usr/bin/gcc-3.3
when compiling my project? Is there an example script somewhere or some file that XCode uses to decide that gcc is located at /usr/bin/gcc-3.3 ? What's the easiest way to redirect it to a different path?
I tried to get it to work, but I'm not a super-expert at shell scripting and I couldn't figure out what exactly XCode is feeding to GCC or exactly how.
The reason I ask is that I want to use a tool called Bullseye coverage. They use faked up versions of GCC (gcc, gcc-3.3, g++, etc.) that requires the real ones to still be at /usr/bin/. Their recommended solution involves creating make files or custom build scripts for everything which is a real hassle.
You could just set the build setting CC to <my-path>/gcc-3.3 in the targets you want built with Bullseye.
Chris
_______________________________________________
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