TIA
> Call me a stupid newbie. But if I want to make an OS X shared library.
> Is that a "framework" project?
Yes. a framework is a shared library + header files + associated data +
documentation, all bundled into something that looks like a single
object in Finder.
> Call me a stupid newbie. But if I want to make an OS X shared library.
> Is that a "framework" project?
A framework typically contains one or more shared libraries. It can
also contain header files, documentation, and other things. It's
basically the libraries plus everything you need to use them. Whether
it's the kind of (presumably Project Builder) project you want depends
on how you want to use the library.
Standard frameworks are found at /System/Library/Frameworks/. Check out
their contents if you want to get more of a first-hand feel for what
they can contain.
--
Tom Harrington, tph (at) pcisys (dot) net
"And you may ask yourself, well, how did I get here?"
-- Talking Heads
What is the difference between a framework and a bundle? Is a bundle a
static library?
> What is the difference between a framework and a bundle? Is a bundle a
> static library?
No. Read
<http://developer.apple.com/techpubs/macosx/Essentials/SystemOverview/ind
ex.html>
hth
meeroh
Thanks Miro. You have pulled my butt out of the fire so many times, I
can't count. :-)
>What is the difference between a framework and a bundle? Is a bundle a
>static library?
A bundle is a whole bunch of files in a specially tagged folder.
The 'bundle' bit on the folder tells the operating-system that
the folder and all its contents should be considered to be one
item.
A framework is one use for bundles. An application is another
user: the executable, all the .tiff images it uses for displaying
icons, and all the HTML files it uses for help files, are all
placed in a bundle. That way, if you copy what you think of as
the application, you're getting all the support files as well.