Dependencies and cleaning?
Dependencies and cleaning?
- Subject: Dependencies and cleaning?
- From: Randall Meadows <email@hidden>
- Date: Tue, 7 Sep 2004 15:43:55 -0400
In Xcode 1.5: I have a project A, which contains an aggregate target
that builds 3 libraries.
I have a project B, which includes project A; all of project B's
targets specify A's aggregate target as a dependency.
When I clean a target in B, all of A's build products (the three
libraries and all their object code) are removed as well. This has
the unfortunate side effect of removing code that a 2nd target in
project B depends upon as well, so even though I only asked for one
target to be cleaned, other targets have to be (mostly) rebuilt as
well (building the libraries takes a lot longer than building just
the target itself).
I haven't tried it, but I assume that a similar thing would happen if
all the targets belonged to the same project, and I'm guessing it's
because of the dependencies.
But separating targets into two projects, in my mind, should make an
external target excluded from the cleansing process, when I
explicitly ask to clean ONE target only.
Is there any way to specify that this "deep cleaning" not be done
with dependent targets? I'm thinking something along the lines of
the "Apply to All" checkbox in the Finder's "Replace" dialog; the
dialog that confirms that I really want to clean the active target
maybe could include a checkbox that says "Also clean dependent
targets"...
randy
_______________________________________________
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.