Arch Linux

Where is documentation on camlimages?
In examples there is OImages.<something>
but I found no OImages-module.

NO API-docs found here: http://gallium.inria.fr/camlimages/#

calimages works fine, jpeg files can be manipulated.
Thanks for updating the package. :-)

libjpeg seems not to be detected (not mentioned as installed)
I use extra/libjpeg-turbo which seems to be the default.
But pacman -U <camlimages-pkg> does not mention the optional libjpeg-pkg as installed.
Not tested camlimages so far, but this may means, I can't use jpeg-files?!

Sure, but I'm not certain we should rely on a third party makefile. And compiling camlimages is already bothersome as is (whacky dependencies on old libraries, etc).

Feel free to make an camlimage-no-omake package on aur as an alternative. Simply add an provides('camlimage') line so that it can work as a dependency for other packages.

What would be great would be to have camlimages compile without the need for omake, which take ages to compile.
An omake-free version of camlimages can be found here:
$ darcs get http://patoline.org/darcs/camlimages
What do you think?

Added a patch so that camlimages can be compiled with giflib 5.1.0 instead of libungif or older versions of giflib.

libungif package no more present in AUR.

camlimages homepage mentions the following file as current file for download:
https://bitbucket.org/camlspotter/camlimages/get/v4.0.1.tar.gz

omake must be mentioned in makedepends-option in the PKGBUILD.

(Ocaml itself maybe also (?)).

Hi, libungif doesn't exist. Please update package, thank you. ;)

Thank you very much rlepigre :)

Removing giflib needed the "-d -d" in my system and then it was really easy !!!

If you are experiencing giflib/libungif problems, here is the only simple way of fixing the problem:
1) Remove ligungif from your system (pacman -R giflib)
2) Modify the PKGBUILD file to remove the libungig dependency (in will work, this should in fact be optional)
3) Run makepkg
4) Install camlimage
5) Install libungif again if some other of you applications require it

This is not a very clean solution but this should work...

An error occured while building:
- build test test.run
+ ocamlfind ocamlc -package graphics -warn-error A -g -I . -I ../src -dllpath ../src -o test.run ../src/camlimages_core.cma ../src/camlimages_all.cma ../src/camlimages_graphics.cma ../src/camlimages_freetype.cma test.cmo -linkpkg
File "_none_", line 1:
Error: Error on dynamically loaded library: ../src/dllcamlimages_all.so: ../src/dllcamlimages_all.so: undefined symbol: PrintGifError

There is a compilation issue with the library libungif (or rather giflib). I am not using GIF images so this is not really a problem for me, but I had to remove libungif from the dependencies in PKGBUILD.

By the way, most of the libraries are optional, so they should be put in the field 'optdepends'.

One more think: it would be great to remove the need for omake...

Here is a quick workaround for anyone who has experienced the following problem while building camlimages v4.0.1:

pngwrite.c: In function 'write_png_file_rgb':
pngwrite.c:65:7: error: dereferencing pointer to incomplete type
pngwrite.c: In function 'write_png_file_index': ] 00161 / 00818
pngwrite.c:174:7: error: dereferencing pointer to incomplete type

This error seems to be fixed in the newer release, just use https://gist.github.com/2793795 as PKGBUILD.

Please correct md5sum to d6b9494b56a72b65fd302d1858efff7c

Thanks for your contribution. I didn't know about OCAMLFIND_DESTDIR, that's why I couldn't make a PKGBUILD for new camlimage.

PKGBUILD for v4.0.1
https://gist.github.com/1090459

Thanks for your contribution. I tried to make the package months ago, but abandonned after repeated failures.

PKGBUILD updated for v3.0.2
https://gist.github.com/661889#file_camlimages_3.0.2_pkgbuild

Added x86_64 flag

No, sorry. It is completely broken.

Clearly an upstream bug. But I will try to find a solution.

If anyone knows how to compile successfully camlimages-3.0.2, I'll gladly update the package.

Makefile.in points to missing files (it's probably a bug, not an unmet dependency on my system). I don't have time for further investigations at the moment.

Please add x86_64 to the supported architecture, builds and runs fine here.