Hi Jon,
just to open my mind, does a framework, according with your previous
explaination, would be GLIB build you ./configure make, but without
the common 'make install' step ?! i mean, the binaries and headers
file shouldn't be fflushed in a /usr/.../include/ and
/usr/.../libs directories, in
There are probably a couple of reasonable approaches. The core portion
of a framework is a shared library. For instance, here's the main
library in OpenLink's iODBC framework:
$ file -L iODBC.framework/iODBC
iODBC.framework/iODBC: Mach-O dynamically linked shared library ppc
GLib could be
programming less painful. The closest thing I could
find is a framework version of GLib 1.2, as part of the GTK+OSX
project.
Can anyone comment on the feasibility / desirability of a
GLib.framework? The primary advantage I see is that a framework is
self contained, which is nice if 'make install
painful. The closest thing
I could find is a framework version of GLib 1.2, as part of the
GTK+OSX project.
Can anyone comment on the feasibility / desirability of a
GLib.framework? The primary advantage I see is that a framework is
self contained, which is nice if 'make install' makes you
A framework is essentially a directory with a particular structure,
conventionally named with a .framework extension. It may contain
libraries, header files, documentation, and other resources. It also
has provisions for versioning, so that, e.g., one framework could
provide support for
