From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Samuel Hornus <samuel.hornus@inria.fr>
Cc: O Caml <caml-list@inria.fr>
Subject: Re: [Caml-list] camlimages problems on mac
Date: Wed, 07 Nov 2012 14:20:37 +0100 [thread overview]
Message-ID: <m2390l35y2.fsf@top.irisa.fr> (raw)
In-Reply-To: <3A52788A-5B74-490E-9678-5C5C1578C524@inria.fr> (Samuel Hornus's message of "Wed, 7 Nov 2012 13:52:18 +0100")
Samuel Hornus <samuel.hornus@inria.fr> writes:
> Hello,
>
> When installing camlimages 4.0.1 with MacPort (Mac OS X 10.7.5, Latest MacPorts),
> the resulting camlimages has no support for JPEG, PNG, PPM, XPM, etc…
> which makes it sort of useless.
>
> When compiling the source using omake, the same happens. It can find
> the header files, but can't find specific functions inside.
>
> The source code for camlimages seems perhaps outdated w.r.t. changes
> in the API of libpng, libjpg, giflib, tifflib, etc…
>
> Could anyone confirms this dire state of affairs? Is there a
> "modernizer" patch floating around? or some work in progress? Is it
> the same on Linux?
I just tried to configure it using godi, and this is what is supported
on my system:
External libraries: lablgtk2 bmp ppm png jpeg tiff freetype(2) ps
Most of my image libraries are installed through homebrew (I see for
instance "jpeg" or "libpng", I don't know where the ppm support comes
from).
To get support for gifs, I installed giflib (still through homebrew).
After doing this, camlimages seems to compile fine.
Alan
next prev parent reply other threads:[~2012-11-07 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 12:52 Samuel Hornus
2012-11-07 13:20 ` Alan Schmitt [this message]
2012-11-07 14:04 ` Samuel Hornus
2012-11-07 14:22 ` AW: " Gerd Stolpmann
2012-11-07 14:30 ` Alan Schmitt
2012-11-07 14:43 ` Pierre-Etienne Meunier
2012-11-13 11:28 ` Samuel Hornus
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=m2390l35y2.fsf@top.irisa.fr \
--to=alan.schmitt@polytechnique.org \
--cc=caml-list@inria.fr \
--cc=samuel.hornus@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