This is the last "major" release of Imlib1. It is depreciated. Please port applications to some other image library (Imlib2, gtk-pixbuf, whatever...). Also note that gdk-imlib WILL NOT WORK with GTK2. It won't even compile. This is not a bug. This is a feature. If you need an image loader for GTK2, use gtk-pixbuf.
imlib-1.9.9: description + notes
Imlib is a general Image loading and rendering library designed to make the task of loading images, and obtaining X-Windows drawables a simple task, as well as a quick one. It also aims to provide simple manipulation routines that might be desired for common operations.
Imlib is an advanced replacement library for libraries like
libXpm
that provides many more features with much greater flexability and speed. If you wish to find out more please read the Imlib tutorial, as it will explain in detail about Imlib, what it does and how it works and how to program using Imlib. It is also the first stop for any programmer if they wish to program using Imlib.
NOTE: Developers intending to use this distribution of imlib for application development should be sure to read the information below. Users installing imlib for the runtime environment only need not read any further.
Developers intending to use this library for development of other freeware packages or their own software applications will need to be familiar with a few peculiarities due to the way that this library is packaged and installed. The reasons for this installation strategy are described further in the fw_common product release notes.
The header files and libraries in this package are installed into /usr/freeware. This means that when building software using this distribution of imlib you should be sure to do the following:
This flag will cause your compilations to correctly find the library's header files at compile time.
- Include the following flag on your compile lines:
- -I/usr/freeware/include
Include the following flag on your link lines:
-L/usr/freeware/lib (if using o32 ABI) -L/usr/freeware/lib32 (if using n32 ABI) -L/usr/freeware/lib64 (if using 64 ABI) This flag will cause the linker to correctly find the library's archive or shared object files at link time.
Additionally, include the following flag on your link lines:
-rpath /usr/freeware/lib (if using o32 ABI) -rpath /usr/freeware/lib32 (if using n32 ABI) -rpath /usr/freeware/lib64 (if using 64 ABI) This flag will allow the binary to locate the shared object library files when the application is run. This is required since the shared objects are stored in these /usr/freeware subdirectories which are not searched by the run-time linker by default.
Finally, if you are building an installable package for inst (contributing to freeware, for example) be sure to make your package depend upon this package. Add the following line to your spec file: prereq ( fw_imlib.sw.lib 1230000000 1239999900 ) Following these guidelines will allow your application to safely and easily use the software in this package.
To auto-install this package, go back and click on the respective install icon.