Custom builds (script phases and rules)?
Custom builds (script phases and rules)?
- Subject: Custom builds (script phases and rules)?
- From: Fredrik Olsson <email@hidden>
- Date: Sat, 06 Aug 2005 18:34:17 +0200
I like to use whatever programming language that fit's my problem best
for the moment, and even mixing them. I also like XCode :).
Anyway some of my projects mix in code written in for example D. The D
compiler I use (gdc) outputs object files just fine, so linking them
with other parts written in for example C is not a problem at all.
So I added a custom rule for compiling *.d files in XCode. Nothing fancy:
gdc -c $(INPUT_FILE_PATH) -g -o $(TARGET_BUILD_DIR)/$(INPUT_FILE_BASE).o
And added
$(TARGET_BUILD_DIR)/$(INPUT_FILE_BASE).o
As an output file.
Well it works, and the compiler gets called and I get my object files.
But they are not linked!
So how do I create a build rule for files, and make XCode aware that it
generated object files that should be linked?
And secondly; after upgrading to XCode 2.1 I get:
/bin/sh: line 1: INPUT_FILE_PATH: command not found
setenv INPUT_FILE_PATH /Users/peylow/Projects/dnuntio/treyst/iff.d
Is is forexample present in the transcript, so I find it wierd.
So in short:
1. How do I add add new compilers to the XCode build path in the most
simple and natural way?
2. Why does the environment variables that worked in 2.0 fail so
miserably in 2.1?
Regards
--
//Fredrik Olsson
Treyst AB
+46-731-513228
email@hidden
_______________________________________________
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