Am 21.03.2009 um 11:13 schrieb an00na:
The Emacs that I've so compiled supports jpeg and png out of box, even though the configure complaints that Emacs is not using -ljpeg or -lpng.
Right! This is support from the OS (with Mail or Preview you can see PNG, JPEG, JPEG-2000, TIFF, GIF ...), and so it's not listed. Invoke for example
otool -L <path to sources>/nextstep/Emacs.app/Contents/MacOS/Emacs #(with optional | sort)
It gives for me:
/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 824.48.0)
/opt/local/lib/libcairo.2.dylib (compatibility version 10803.0.0, current version 10803.6.0)
/opt/local/lib/libdbus-1.3.dylib (compatibility version 8.0.0, current version 8.0.0)
/opt/local/lib/libgdk_pixbuf-2.0.0.dylib (compatibility version 1401.0.0, current version 1401.7.0)
/opt/local/lib/libglib-2.0.0.dylib (compatibility version 1801.0.0, current version 1801.3.0)
/opt/local/lib/libgmodule-2.0.0.dylib (compatibility version 1801.0.0, current version 1801.3.0)
/opt/local/lib/libgobject-2.0.0.dylib (compatibility version 1801.0.0, current version 1801.3.0)
/opt/local/lib/libintl.8.dylib (compatibility version 9.0.0, current version 9.2.0)
/opt/local/lib/libncurses.5.dylib (compatibility version 5.0.0, current version 5.0.0)
/opt/local/lib/librsvg-2.2.dylib (compatibility version 25.0.0, current version 25.3.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.1.12)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
You can also try to view graphics files of different types to find out what already is supported – or check the variable image-types (svg png gif tiff jpeg xpm xbm pbm). In GNU Emacs 23 you're able to see a lot of formats displayed directly. If you see some binary garbage in the buffer, then C-c C-c will convert it to a picture (watch both times the mode-line) – and back!
However, I'm not clear what's going on behind the scene, or what are the conditions of other libs.
You could check the file config.log – though the configure run much too often creates only a useless castrated version of a few hundred bytes length (could be a 'make clean' or 'make distclean' cancels this "feature" for the next configure). Another option is build Emacs in a *compilation* buffer:
M-x compile RET
delete the text and insert the configure command, then change it to contain:
... sh -x ./configure ...
This will produce a few thousand lines of output and show you when and why configure fails to find or determine something. Save the buffer (best also close it, because a subsequent compilation can overwrite it), then continue to work, i.e., investigate the errors by newly opening the saved file (can take minutes of fontification) and/or let Emacs build a new version.
Got Mole problems?
Call Avogadro 6.02 x 10^23