• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: including library in .app
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: including library in .app


  • Subject: Re: including library in .app
  • From: "John C. Randolph" <email@hidden>
  • Date: Fri, 31 Jan 2003 14:21:49 -0800

I asked around about this, and was told:

This should work just fine. The Frameworks folder should be created as
needed, and the framework should end up inside the app bundle. You may want
to find out if this developer is making the mistake of having the copy files
build phase be in the framework's target instead of the application's target
- this is the usual source of confusion.

-jcr

On Friday, January 31, 2003, at 11:11 AM, 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.


John C. Randolph <email@hidden> (408) 974-8819
Sr. Cocoa Software Engineer,
Apple Worldwide Developer Relations
http://developer.apple.com/cocoa/index.html
_______________________________________________
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.

References: 
 >Re: including library in .app (From: Tito Ciuro <email@hidden>)

  • Prev by Date: extending NSString - (NSData *)dataUsingEncoding:(NSStringEncoding)encoding
  • Next by Date: cursor bigger than 16*16
  • Previous by thread: Re: including library in .app
  • Next by thread: Re: including library in .app
  • Index(es):
    • Date
    • Thread