$ file -L iODBC.framework/iODBC iODBC.framework/iODBC: Mach-O dynamically linked shared library ppc
GLib could be compiled directly into this library. This would involve modifications to the build, or maintaining a parallel OS X-only build system (e.g., an Xcode project).
A simpler approach would be to build a framework wrapper around the GLib libraries. This would build GLib with the autotools, then build a framework that depends on (and, probably, includes) the built libraries.
Anyhow, I was hoping someone who had gone down this road could offer some advice. I don't want to burden this list with any more traffic specific to one platform.
On Apr 29, 2005, at 10:57 AM, Antonio Gomes wrote:
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 a spread way !!
Best Regards
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 both GLib 1.2 and 2.0. See the following article, if you're interested:
Mac OS X Frameworks
<http://developer.apple.com/documentation/MacOSX/Conceptual/ BPFrameworks/index.html>
The question is about building / packaging / deploying GLib and GLib-based applications on OS X, where a framework may be more desirable than a 'make install' in /usr/local.
On Apr 28, 2005, at 3:29 PM, Sven Neumann wrote:
What the heck is a "framework" and why don't you just use glib on OS X?
It compiles and works just fine.
_______________________________________________ gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
