Direct Dependencies, multiple links to classes and Zero Link?
Direct Dependencies, multiple links to classes and Zero Link?
- Subject: Direct Dependencies, multiple links to classes and Zero Link?
- From: Peter Borg <email@hidden>
- Date: Mon, 19 Jul 2004 12:15:49 +0200
Hi!
I am working on project (Smultron, http://smultron.sourceforge.net/ if
anyone is interested in checking it out...) to which I've recently
added a command-line tool as a separate target. This tool (smultron) is
added into the bundle of the application (Smultron) when building, and
if I first build smultron (the tool) and then Smultron (the app)
everything works fine. But I thought I might add smultron (the tool) as
a Direct Dependent(?) of Smultron (the app) and then the problems
begin. It starts to compile smultron (the tool) but it stops after a
while with many errors saying that it can't find the classes of
Smultron (the app) - the tool and the app don't share any classes. This
only happens in the Deployment build and not in Development and if you
turn on Zero Link in Deployment you can complie everything without
errors, but this is obviously something you don't want to do. You can
also fix it by linking all the classes and frameworks of Smultron (the
app) into the target of smultron (the tool) but this makes everything
compile twice and does not seem like a good solution.
So my question is: is this how it should be or am I missing something
fundamental? To me it seems that if I build them separately without any
problems I should be able to build one after the other in a "chain"
also without any problems.
(The same thing happens if I put the two targets into an aggragate
target.)
Regards,
Peter Borg
_______________________________________________
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.