Re: including library in .app
Re: including library in .app
- Subject: Re: including library in .app
- From: Pete Carss <email@hidden>
- Date: Sat, 1 Feb 2003 00:17:58 +0000
I'm a bit confused now...
the apple documents I think are describing two distinct stages one for
when you compile the framework, to create a framework that can be put
in the application, and one for when you compile your project. Here's
my confusion though...
from 'Cocoa Programming'
"A framework built for embedding inside an application will not work
when installed in /Library/Frameworks. A framework built to be
installed at /Library/Frameworks cannot be embedded inside an
application'
a quick gander at "
http://www.zveno.com/open_source/libxml2xslt.html";
the place where I got the pre-compiled framework shows:
"These libraries have been built as OS X Frameworks. This means that
you may install them anywhere on your system, or within your
application, and OS X will search for them. Suggested installation
locations are /Library/Frameworks or ~/Library/Frameworks"
so what gives?
Pete
On Friday, Jan 31, 2003, at 19:11 Europe/London, Tito Ciuro wrote:
Pete,
What a coincidence, I want to do this as well! :)
On Friday, January 31, 2003, at 06:51 PM, Pete Carss wrote:
is there a procedure for getting PB to include a framework in the
.app so as to avoid the user having to install the framework? I'm
thinking here of libxml, I don't want to send my users down the unix
route of having to install this library or that library...
I tried this and it works... almost. Start with this:
http://developer.apple.com/techpubs/macosx/DeveloperTools/
ProjectBuilder/ProjectBuilder.help/Contents/Resources/English.lproj/
Frameworks/Embedding_a_Application.html
This are the docs I've followed to add a framework to my project. It
works... partially: I followed the steps very carefully and the only
problem seems with the Copy Files phase. Supposedly, the Framework in
question should be copied to the Contents/Frameworks/ directory, but
it doesn't.
The documentation doesn't state clearly whether the Frameworks
directory within the app is automatically generated prior to copying
the Framework there. It should, I guess... no?
However, if I create the 'Frameworks' directory within 'Contents' and
copy the framework manually, everything is perfect. Of course, I add
the Framework and directory manually *after* PB has generated the app.
No dependencies are created externally, which is exactly what I
wanted. I know that because I copied the app to my TiPB, which doesn't
have a clue about the Framework I'm using :)
So the docs do not tell the whole story, it seems. Perhaps the Copy
Files phase fails because the Frameworks directory isn't there. If
this is so... what do I have to do to create this directory in a
process [generating the app] that is already fully automatic?
BTW... I tried two things: in PB, I placed my Framework inside the
Frameworks folder. Nothing. Then I tried to place it in the Other
Frameworks folder. Nope. So at this point, this "hidden" step puzzles
me.
Am I leaving something really obvious aside? Does PB need an extra
step to make the Frameworks folder to be generated prior to the Copy
Files phase?
I'd love to know...
-- Tito
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.