From: Kuba Ober <ober.14@osu.edu>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] native GTK+ on Mac OS X
Date: Mon, 30 Mar 2009 10:08:59 -0400 [thread overview]
Message-ID: <8B15BB4E-3423-483D-8A96-DAD66DFA4B71@osu.edu> (raw)
In-Reply-To: <2B4B31CE-5C55-4F07-AC9C-84307AF1F7C2@cea.fr>
>
>
> 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.
I have been running macports and gtk2 compiled +quartz +no_x11 for
quite a while now. The only snag is that instead of installing pango
you have to install pango-devel, as there is a bug that prevents pango
from compiling w/o x11 support in current MacPorts.
I'm running native gimp and other tools, and it all "just works", so I
don't
really see why you'd even need the x11 gtk.
Kuba
next prev parent reply other threads:[~2009-03-30 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090330100002.CA4F0BBC6@yquem.inria.fr>
2009-03-30 10:56 ` Pascal Cuoq
2009-03-30 14:08 ` Kuba Ober [this message]
2009-03-30 14:12 ` [Caml-list] " Joel Reymont
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8B15BB4E-3423-483D-8A96-DAD66DFA4B71@osu.edu \
--to=ober.14@osu.edu \
--cc=caml-list@yquem.inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).