> On Mar 30, 2009, at 7:41 AM, Grünewald Michaël wrote:
>
>> Did you have Gtk+ working natively in OSX?

Joel Reymont <joelr1@gmail.com> wrote:

> I do but I built from source after downloading the GTK+/OSX frameworks
> and using ./configure --with-quartz
>
> I also had to place the following two (identical) files in /opt/local/
> lib/pkgconfig since my pkg-config comes from MacPorts

Alternately, I have found that I could use
MacPorts for everything GTK+ and still get the Quartz
back-end if I follow the instructions for compiling
a native Mac OS X version of Inkscape:

http://www.inkscape.org/wiki/index.php/CompilingMacOsX

For distributing binaries, I build my quartz variant of MacPorts
as a subdirectory of the installation path that I wish to use
(/usr/local/Frama-C/lib/macports), and include in the distributed
archive those libraries that are necessary for running Frama-C.
See the contents of one of the Mac OS X distributions
for details: http://frama-c.cea.fr/download.html

This unfortunately means that the
binaries can not be installed anywhere else.
Gimp.app (http://gimp-app.sourceforge.net/) allows
to move the application around by using a shell script
to change, at each launch, the paths in all the configuration
files that have them hard-coded. But some of the libraries
that Frama-C depends on seem to have binaries files
with hard-coded paths, so I didn't succeed in doing the
same thing.

Tangentially, I would be interested in any improvement
suggestions from people more knowledgeable that me
on the subject of gtk-quartz, displaying unicode with
pango on Mac OS X, and their interactions with OCaml.

Pascal