RE: Cross-project Reference and Targets
RE: Cross-project Reference and Targets
- Subject: RE: Cross-project Reference and Targets
- From: "Randy Widell" <email@hidden>
- Date: Wed, 30 May 2007 14:17:47 -0400
> > As far as I can tell, this is not true. The project reference only
> > contains
> > a reference to the project's product(s), and products cannot be
> > added to a
> > target as a dependency.
>
>
> * Open the Inspector for the local target. Select the General tab.
> * Click the plus button in the lower left to open the sheet to select
> from available targets.
>
> Is the remote project + targets not listed on that sheet?
Seems like I tried that earlier, but maybe not. Anyway, it worked. Thank
you, very much.
I ran into another problem, though. I am creating an app with a private
framework. I have the app target setup to link against the private
framework and copy it to the Frameworks folder in the app's bundle. That
works fine. However, my framework needs to link against the framework to
which my project refers (ObjectiveLib). I have my framework setup to link
against and copy the ObjectiveLib framework into the Frameworks folder in
its bundle.
When I build, ObjectiveLib builds fine, my framework builds fine, but my app
has a warning stating that the linker could not find ObjectiveLib in
MacOSX10.4u.sdk/Library/Frameworks.
So, I modified my app's target to link against ObjectiveLib directly. That
took care of the warning. When I try to debug, however, I get an exception
stating that ObjectiveLib (referenced from my app) could not be found in
/Library/Frameworks.
Finally, I tried modifying the app target to copy ObjectiveLib into its
Frameworks folder (which seemed redundant), and I still get the exception
when trying to debug the app.
_______________________________________________
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