Commit 5b6dcdc0 authored by Paolo Bacchilega's avatar Paolo Bacchilega
Browse files

Initial revision

Paolo Bacchilega <>
Josua Groeger <>
Chauk-Mean Proum <>
This diff is collapsed.
Basic Installation
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.
The file `' is used to create `configure' by a program
called `autoconf'. You only need `' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
Compiling For Multiple Architectures
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
Installation Names
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.
If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.
Sharing Defaults
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/' if it exists, then
`PREFIX/etc/' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Operation Controls
`configure' recognizes the following options to control how it
Use and save the results of the tests in FILE instead of
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
debugging `configure'.
Print a summary of the options to `configure', and exit.
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
Print the version of Autoconf used to generate the `configure'
script, and exit.
`configure' also accepts some other, not widely useful, options.
## Process this file with automake to produce
libgthumb \
src \
components \
doc \
omf-install \
desktopdir = $(datadir)/applications
desktop_DATA = $(
applicationsdir = $(datadir)/application-registry
applications_DATA = gthumb.applications
icondir = $(datadir)/pixmaps
icon_DATA = gthumb.png
man_MANS = gthumb.1
acinclude.m4 \
add-include-prefix \ \
gthumb.spec \ \ \ \
omf.make \
xmldocs.make \
$(applications_DATA) \
$(desktop_in_files) \
$(desktop_DATA) \
$(icon_DATA) \
version 1.105
* Use gconf as configuration system instead of gnome-config.
version 1.104
* New tool: find duplicates.
* Added an image properties dialog that displays various image
properties and EXIF data if present (you need the libexif).
* Added ability to print the comment alongside the image.
* Added option to choose the click policy.
* Added "duplicate image" operation.
* Better handling of long comments.
* The image view component now supports printing, so you can print
an image (and its comment) using Nautilus.
version 1.103
* New tool: jpeg lossless transformations.
* The user can edit/view comments and delete images in fullscreen
* Changed the fourth layout type to something more usefull.
* Automatically update the content of a folder.
version 1.102
* New tool: rename series of images.
* Added a maintenance dialog where the user can delete old/all
comments/thumbnails, and backup and restore comments.
* Added header and footer support to the "Index Image" tool.
* Re-added the "Toolbar Style" option.
* Added Next/Prev Image buttons on toolbar.
* Click on an image to view the next one.
* Minor usability improvements.
* Bugfixes.
version 1.101
* Changed arrangement of menus.
* Preload next 2 images and previous one when browsing.
* Added ability to view an image in black and white.
* Bugfixes.
* Removed a few memleaks.
version 1.100
* Ported to GNOME 2.
* Added ability to go back and forward in history.
* Added ability to rename and delete folders.
* Better error reporting.
* Removed redundant options.
version 0.10
* Improved usability of the "Open with" dialog.
version 0.9.9
* View fullscreen directly from the contextual menu of a thumbnail.
* Option to switch automatically to full screen mode when the
slideshow starts.
* The user can specify an editor different from the ones associated
with images.
* Bugfixes.
version 0.9.8
* Minor features added.
* Bugfixes.
version 0.9.7
* Bugfixes.
version 0.9.6
* Selection works better when directories contain a lot of files.
* The location entry can stay on a separate toolbar.
* More keyboard shortcuts.
* Added "fit image to window only if larger" mode.
* Bugfixes.
version 0.9.5
* Added a search tool.
* Made an image viewer component.
* New icon.
* Bugfixes.
version 0.9.4
* Bugfixes.
version 0.9.3
* New feature: Add comments to images.
* Ask what to do when trying to overwrite a file.
* Bugfixes.
version 0.9.2
* Fixed RPM build.
* Added 2 more layouts (Josua Groeger).
version 0.9.1
* New feature: Save thumbnails as single image.
* Various usability improvements.
* Mouse wheel support.
version 0.9
* Faster zooming.
* Added a navigation window ala GIMP.
* Fully usable with the keyboard.
* Added a little manual.
* Can accept multiple directories at command line.
version 0.8
* Uses Gnome-VFS.
* Bugfixes.
version 0.7.2
* Added print support (optional).
* Fixed gdk-pixbuf detection.
version 0.7.1
* Translations: French, Japanese.
version 0.7
* New option: Thumbnails size.
* Added history menu.
version 0.6.4
* Bookmarks are in a menu now (ala Nautilus).
* Bugfixes.
version 0.6
* New thumbnails view.
* New option: change window layout.
version 0.5
* New options: transparency type, checks color and size (ala Gimp).
* Rotate, Flip and Mirror image (not for animations).
* Faster image scrolling.
version 0.4
* Play GIF animations.
* Drag & Drop.
* Use Nautilus thumbnails (read only).
version 0.3
* Options dialog.
* TAB completion in location entry.
* More keyboard shortcuts.
* Translations: Dutch, Korean.
version 0.2
* First public version.
This is the distribution of gThumb, an image viewer and browser utility
for the GNOME environment.
* Features
gThumb lets you browse your hard disk, showing you thumbnails of image
files. It also lets you view single files (including GIF animations), add
comments to images, organize images in catalogs, print images, view
slideshows, set your desktop background, and more.
* Licensing
This program is released under the terms of the GNU General Public
License (GNU GPL).
You can find a copy of the license in the file COPYING.
* Dependencies
In order to use this program you need a working GNOME environment
version 2, with the development tools installed properly. The following
is the detailed list of libraries you need:
* glib version 2.0.0
* gtk version 2.0.0
* libxml version 2.4.0
* libgnome version 2.0.0
* libgnomeui version 2.0.0
* libgnomecanvas version 2.0.0
* gnome-vfs version 2.0.0
* libglade version 2.0.0
* bonobo-activation version 1.0.0
* libbonobo version 2.0.0
* libbonoboui version 2.0.0
* libgnomeprint version 1.110
* libgnomeprintui version 1.110
If you want to view EXIF data attached to images, you need the libexif
library that can be found at this web site :
#undef PACKAGE
#undef VERSION
dnl check for working fnmatch(3)
[AC_MSG_CHECKING(for working fnmatch with FNM_CASEFOLD)
[rm -f conftestdata; > conftestdata
AC_TRY_RUN([#include <fnmatch.h>
main() { exit(fnmatch("/*/bin/echo *", "/usr/bin/echo just a test", FNM_CASEFOLD)); }
], fr_cv_func_fnmatch=yes, fr_cv_func_fnmatch=no,
rm -f core core.* *.core])dnl
if test $fr_cv_func_fnmatch = yes; then
sed -e 's/^/ /' -e 's/ \+$//' -e 's/ \+/ -I /g' -e 's/^ \+//'
# Run this to generate all the initial makefiles, etc.
srcdir=`dirname $0`
test -z "$srcdir" && srcdir=.
(test -f $srcdir/ \
&& test -f $srcdir/ChangeLog \
&& test -d $srcdir/src) || {
echo -n "**Error**: Directory "\`$srcdir\'" does not look like the"
echo " top-level $PKG_NAME directory"
exit 1
which || {
echo "You need to install gnome-common from the GNOME CVS"
exit 1
SUBDIRS = image-viewer catalog-view
<oaf_server iid="OAFIID:GNOME_GThumb_CatalogView_Factory" type="exe"
<oaf_attribute name="repo_ids" type="stringv">
<item value="IDL:Bonobo/GenericFactory:1.0"/>
<oaf_attribute name="name" type="string"
value="GThumb Catalog View Factory"/>
<oaf_attribute name="description" type="string"
value="Factory for the GThumb catalog view control"/>
<oaf_server iid="OAFIID:GNOME_GThumb_CatalogView" type="factory"
<oaf_attribute name="repo_ids" type="stringv">
<item value="IDL:Bonobo/Unknown:1.0"/>
<item value="IDL:Bonobo/Control:1.0"/>
<item value="IDL:Nautilus/View:1.0"/>
<oaf_attribute name="name" type="string"
value="GThumb Catalog View control"/>
<oaf_attribute name="description" type="string"
value="GThumb Catalog View control"/>
<oaf_attribute name="bonobo:editable" type="boolean" value="false"/>
<oaf_attribute name="bonobo:supported_mime_types" type="stringv">
<item value="x-directory/*"/>
<oaf_attribute name="nautilus:view_as_name" type="string"
<oaf_attribute name="nautilus:view_as_label" type="string"
_value="View as Catalog"/>
<oaf_attribute name="nautilus:viewer_label" type="string"
_value="GThumb Catalog View"/>
<cmd name="PrintImage" _label="_Print"
_tip="Print the current image" pixtype="stock"
pixname="Print" accel="*Control*p"/>
<submenu name="File">
<placeholder name="File Items Placeholder">
<menuitem name="PrintImage" verb=""/>
libexec_PROGRAMS = gthumb-catalog-view