Re: Can't build correctly with sub-projects
Re: Can't build correctly with sub-projects
- Subject: Re: Can't build correctly with sub-projects
- From: Mark Munz <email@hidden>
- Date: Sun, 14 Mar 2004 08:16:36 -0700
On Mar 13, 2004, at 9:03 PM, Jim Correia wrote:
On Mar 13, 2004, at 10:47 PM, Mark Munz wrote:
I've been banging my head on this for some time and can't figure out
what Xcode is doing.
I'm trying to use sub-projects under Xcode (much like Codewarrior).
I've dragged in an external app2.xcode project file. I then take the
contents of the project (app2.app) and use a Copy Files Build Phase
to copy the file to the project's bundle.
Unfortunately, Xcode complains that "No such file or directory"
exists. This is no true, since I verified that the external project
did build and has the file in the build folder.
This should be a known bug at this point (I've filed a similar bug).
The release notes mention that sub-projects work best when they share
a common build folder. In this case, if they don't share a common
build folder, your copy phase will fail.
Setting a comment build folder globally (in the prefs) or per project
(project inspector) should solve your problem.
Jim
Thanks for the help -- I am finally able to get my project to build
with the additional components. Once I got one sub-project to work, the
solution worked for the other components I needed to build and include
in my app.
I couldn't find any reference to the bug (or sub-projects) in the
release notes, but setting the output folder of all my sub-projects to
the main one solved the problem. I would definitely consider that a
bug and I hope Apple doesn't think that because there's a work-around
for it, it doesn't need much attention.
On Mar 13, 2004, at 11:46 PM, Julien Dufour wrote:
Same problem here. If my memories are right, this functionality was
working fine in a previous release and has been broken. A simple
workaround consists in adding the product (located in the build folder
of the sub-project) to the super-project like a regular file. This
file reference can then be included in various build phases instead of
the product reference of the sub-project.
Moreover, everyone should be very careful with the references to the
products of the sub-projects. I have found another problem regarding
them: they cannot be removed from the build phases and I suspect their
inclusion to be a possible source of corruption of the projects (Xcode
generates errors when opening the project). Is anybody experiencing
the same issue?
Julien Dufour
It seems like Xcode isn't quite fleshed out on the sub-project
category. I've had a couple instances where some of the sub-projects
weren't getting updated and copied over correctly. Had to manually
massage them as well, but nothing I can reproduce regularly.
I'll make sure to keep regular backups of the project to avoid
corruption problems. Hopefully Apple will put a little more focus on
this part of Xcode, since my projects often times require 2 or more
components (in this case, I believe I have 6-7 projects -- 6 component
pieces that are put into a 7th application bundle).
Mark Munz
_______________________________________________
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.