Cross-project dependencies and frameworks
Cross-project dependencies and frameworks
- Subject: Cross-project dependencies and frameworks
- From: Yann Bizeul <email@hidden>
- Date: Mon, 29 May 2006 10:12:15 +0200
Hello there.
I have a project for which I must provide source code to a customer,
I'd like to do this by giving them svn access to the repository.
They can access the application source code, but not the code of some
frameworks used in this application.
So I tried to play with cross project dependencies, and that is where
troubles began.
Say a project called PrivateFramework in its own directory, I include
the xcodeproj file of this project in my application, and use
products listed below to link with and use in copy build phase of my
main application.
The problem is that public headers of this framework do not appear in
my application project (expanding the triangle shows no files) and
the build fails. If I add by "existing framework..." the framework
build, everything is fine, I see the headers.
I red somewhere that I should use common build locations for every
parts of my projects, that's what I did, without success.
#import <PrivateFramework/header.h> does not work.
According to you, should I file a bug report, or am I missing
something obvious in the doc about that ?
Thanks for your help.
Yann Bizeul • yann at tynsoe.org
Cocoa Developer
Tynsoe Projects
BuddyPop • GeekTool • SSH Tunnel Manager • ...
http://projects.tynsoe.org/
_______________________________________________
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