Re: Adding/moving a custom executable to "project" level
Re: Adding/moving a custom executable to "project" level
- Subject: Re: Adding/moving a custom executable to "project" level
- From: Malte Tancred <email@hidden>
- Date: Fri, 7 May 2004 16:41:18 +0200
On 6 maj 2004, at 14.22, Malte Tancred wrote:
Is there a way to add (or move an already existing) custom executable
from user level to project level?
Following up on my own question...
I poked around a bit in the .xcode file wrapper and found
default.pbxuser.
It contains a default executable configuration for the project in
question,
and from my tests it appears the information in this default
configuration
is added to all <user>.pbxuser upon creation (FYI, the project in
question
is a "Java Tool"). Just for fun I manually added another executable to
the
default.pbxuser file, removed my <user>.pbxuser and reopened the
project.
Voil`! It worked. A new .pbxuser was created with two executables in it.
However, it seems a bit sad that creating a (Legacy) Java Tool _target_
in
an already existing project doesn't produce a target with properties
equal
to the default target of a newly created Java Tool _project_. I've found
this a bit confusing. Also, the default.pbxuser hack only works the
first
time someone opens the project. Changes made to the executable after the
project has been opened will only affect the user doing the changes.
I dunno, maybe I'm just missing the idea with defining custom
executables.
Thoughts anyone?
Cheerio,
Malte
--
Malte Tancred
Computer Programmer
Oops AB, http://oops.se/
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.