• 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: Framework library...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Framework library...


  • Subject: Re: Framework library...
  • From: Charles Jolley <email@hidden>
  • Date: Tue, 16 Jul 2002 12:48:22 -0500

Is there a way to build something like the lib*.a file, only using Objective-C/cocoa instead of Carbon?

Easy. Create a new Target in your Project Builder application and select "Library." This is preconfigured to generate a statically linked library.

Remember, however, that libraries (dynamic and static) are different that Frameworks. A framework is a bundle that contains a dynamic library and all its associated resources and headers. The library is the executable code only. Also, developers can remove any resources from your framework that will not be needed at runtime when they distribute it inside their own application bundles.

-C

On Tuesday, July 16, 2002, at 12:01 PM, Josh Ferguson wrote:

That's certainly an idea. The issue, however, is that I cannot believe that there isn't a way to create some kind of library/framework that is statically linked into the application. Our SDK already has a static Mach-O library, but I want to simplify things by creating an Objective-C frontend for it. Requiring them to include even more files seems to be complicating things. I'm convinced that I'm missing something extremely basic. Is there a way to build something like the lib*.a file, only using Objective-C/cocoa instead of Carbon?

-----Original Message-----
From: Mike Beam [mailto:email@hidden]
Sent: Tuesday, July 16, 2002 11:50 AM
To: cocoa-dev
Subject: Re: Framework library...


Actually, I was just being stupid. It was too early when I wrote this up, and
I realized that it's not a build time error but a runtime error. It's
treating the framework as a dynamic library instead of a static library (like
I want), and I didn't have the framework in the frameworks directory. The
wrapper is wrapping around a static library (there is a dynamic library that
is already installed on the machine), so how would I go about statically
linking a framework to an application (so the framework doesn't have to be on
the end user's machine). There must be a method, I just can't figure it out!

I haven't been following this thread too closely, so forgive me if my
response has been mentioned already, or whatnot. Would it be sufficient to
include the framework inside of your application's bundle? OmniWeb does
this in the directory OmniWeb.app/Contents/Frameworks. This would still have
the framework on the end users machine, but they don't have to know about
it.

Mike Beam
_______________________________________________
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.
_______________________________________________
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.

  • Prev by Date: Re: PBX alternative?
  • Next by Date: Re: PBX alternative?
  • Previous by thread: RE: Framework library...
  • Next by thread: Comment on NSThread
  • Index(es):
    • Date
    • Thread