Xcode stripping subproject dependencies?
Xcode stripping subproject dependencies?
- Subject: Xcode stripping subproject dependencies?
- From: Bertrand Landry-Hetu <email@hidden>
- Date: Wed, 13 Jul 2005 18:59:34 -0700
Hi everybody,
I'm trying to convert my projects from 2.0 to 2.1 and ran into a
really weird situation with project dependencies. When I set my inter
project dependencies, some will disappear when I quit Xcode and open
the project again.
I have 2 project files with 3 target on each. So let say project foo
and bar have targets foo1, foo2 foo3 & bar 1 bar 2 bar 3. Inside each
project the dependencies are set like this, bar 2 depends on bar 3,
bar 1 depends on bar 2 & bar 3, foo2 depends on foo3, foo1 depends on
foo2.
Now the tricky thing is that foo 2 depends on bar 2 & bar 3 and foo 1
depends on bar 1, 2 & 3. I have set those dependencies in xcode, I do
a clean build and it works perfectly. I quit xcode, check in the
changes in my perforce repository, reopen the file and poof, the only
external dependency left is foo1 on bar 1, but since it does not
happen to be in the right order my build fail on foo2 that gets build
before bar 1. (confusing eh ?) At that point I do a diff of the
project file from perforce and perfoce has the deps but the local file
has lost all traces of them. My guess is Xcode strips them out when it
loads the file.
Anybody has any ideas of what is causing this? workarounds ?
Thanks.
Bertrand.
_______________________________________________
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