Re: Make XCode automatically link files produced by shell script phase
Re: Make XCode automatically link files produced by shell script phase
- Subject: Re: Make XCode automatically link files produced by shell script phase
- From: Michael Casteel <email@hidden>
- Date: Fri, 17 Jun 2005 15:57:46 -0700
On 6/17/05, Jonas Maebe said:
>So my question is: what do I have to do to get XCode to perform a
>linking step in this situation (without requiring users to manually
>add all the .o files to the linking phase), and how can I tell it
>which objects to use? In the help I found some information about
>preprocessing custom files into C code and feeding them back to XCode,
>but putting my .o files in the mentioned DERIVED_FILES_DIR does not do
>anything either.
I'm making progress (also Free Pascal) by suppressing the assemble in
fpc so that my 'with output files:' for my Pascal build script ends in
.s (in my case, $(OBJECT_FILE_DIR)/$(INPUT_FILE_BASE).s). Then, Xcode
picks up the assembler source and manages the assembly then link. Oh, I
have the ppcppc flags -s -al so ppcppc seems to just generate the
assembler output when compiling.
Then my link fails with:
/usr/bin/ld:
/Volumes/Data/mac/pKlondike/build/pCarbon.build/Release/pCarbon.build/
Objects-normal/ppc/Cards.o relocation overflow for relocation entry 584
in section (__TEXT,__text) (displacement too large)
But, I feel like I'm getting closer.
Oh, and I had to add this to 'other linker flags' in the Build tab for
my target:
/usr/local/lib/fpc/2.0.0/units/powerpc-darwin/rtl/system.o
/usr/local/lib/fpc/2.0.0/units/powerpc-darwin/rtl/macpas.o
/Developer/Pascal/UPInterfaces/Carbon.o
Is there a better place to put these do you think?
--
Mike Casteel
email@hidden Seattle, WA
_______________________________________________
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