i have two self-written frameworks, lets call em "foo.framework" and
"bar.framework". i'm not sure if that's relevant, but "bar" depends on
"foo".
i now build a Cocoa application that links against "foo". because i
don't want to have top deploy "foo.framework" externally, my app has a
Copy Files build phase, which copies "foo.framework" to the ./
Framework subfolder of my app bundle. this works fine, i can run the
app, it loads and uses "foo", and all is dandy.
now i add a reference to "bar" to my app. again, i set it to be copy
into my bundle (which it does - both frameworks show up after a build).
however, if i now run my app, it fails, and the console claims that "/
User/me/Library/Frameworks/bar.framework" could not be found. that's
of course correct (the framework isn't deployed there), but why
doesn't my app just load it from the bundle, as it does with "foo"? if
i manually deploy the library to "/User/me/Library/Frameworks", all
works fine of course.
i cannot see any tangible difference between the two projects (except
that one references the other), and they were both added to the app
project in the same way [i tried this with several apps, both show the
same behavior - so i'm fairly certain it's not a misconfig in my app
project].
any idea what could be causing the one framework to not be found from
inside the bundle, while the other is? could some setting in the
framework project that i'm overlooking be causing this? or could this
this due to the reference?
any suggestions or ideas wouild be appreciated.
thanx,
marc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
