Commit 461bd357 authored by Kevin Cozens's avatar Kevin Cozens Committed by Kevin Cozens
Browse files

Released a version 1.1.0 tarball. This is the first development release

2006-09-20  Kevin Cozens  <kcozens@cvs.gnome.org>

	Released a version 1.1.0 tarball. This is the first development
	release for use with the 2.3/CVS version of GIMP.

	* configure.in: Bumped required versions of glib and gtk+ to match
	the versions needed by the CVS version of GIMP.

	* INSTALL: Updated this file with something a bit more useful than
	the standard default generic information.
parent 7d17de0e
2006-09-20 Kevin Cozens <kcozens@cvs.gnome.org>
Released a version 1.1.0 tarball. This is the first development
release for use with the 2.3/CVS version of GIMP.
* configure.in: Bumped required versions of glib and gtk+ to match
the versions needed by the CVS version of GIMP.
* INSTALL: Updated this file with something a bit more useful than
the standard default generic information.
2006-09-19 Kevin Cozens <kcozens@cvs.gnome.org>
* NEWS: Updated the information about the 1.1.0 release.
......
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
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, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)
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 you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'. You only need
`configure.ac' 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
documentation.
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. Run `./configure --help'
for details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
*Note Defining Variables::, for more details.
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 support 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 architecture.
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' cannot figure out
automatically, but needs to determine by the type of machine the package
will run on. Usually, assuming the package is built to be run on the
_same_ architectures, `configure' can figure that out, but if it prints
a message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:
CPU-COMPANY-SYSTEM
where SYSTEM can have one of these forms:
OS KERNEL-OS
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 machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the `--target=TYPE' option to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
Installation instructions for GIMP 2.3
--------------------------------------
Sharing Defaults
================
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' 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.
Defining Variables
==================
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
will cause the specified gcc to be used as the C compiler (unless it is
overridden in the site shell script).
`configure' Invocation
======================
Here are some basic steps to building and installing the Tiny-Fu plug-in
for the 2.3/CVS version of GIMP.
The most important part of building Tiny-Fu is to make sure the requirements
for building it are fulfilled. It depends on a number of tools and libraries
which are listed below. For libraries this means you also need to have the
header files installed.
******************************************************************
* Unless you are experienced with building software from source, *
* you should not attempt to build all these libraries yourself! *
* We suggest that you check if your distributor has development *
* packages of them and use these instead. *
******************************************************************
1. You need to have installed a recent version of pkg-config available
from http://www.freedesktop.org/software/pkgconfig/.
2. You need to have installed GTK+ version 2.8.17 or newer. Tiny-Fu
needs an even more recent version of GLib (>= 2.10.2). Sources
for these can be grabbed from ftp://ftp.gtk.org/.
3. You need to have installed a version of GIMP that was built from a
2.3 source tarball or from CVS.
4. Configure Tiny-Fu by running the 'configure' script. You may want
to pass some options to it, see below.
`configure' recognizes the following options to control how it
operates.
5. Build Tiny-Fu by running 'make'. The use of GNU make is recommended.
If you need to tweak the build to make it work with other flavours
of make, I'd appreciate if you would send a patch with the changes.
`--help'
`-h'
Print a summary of the options to `configure', and exit.
6. Install Tiny-Fu by running 'make install'.
`--version'
`-V'
Print the version of Autoconf used to generate the `configure'
script, and exit.
If you have any old GLib or GTK+-2.x libraries lying around on your
system, configure may fail to find the new ones.
`--cache-file=FILE'
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
disable caching.
`--config-cache'
`-C'
Alias for `--cache-file=config.cache'.
Generic instructions for configuring and compiling auto-configured
packages are included below. Here is an illustration of commands that
might be used to build and install GIMP. The actual configuration,
compilation and installation output is not shown.
`--quiet'
`--silent'
`-q'
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).
% tar xvfz gimp-tiny-fu-1.1.x.tar.gz # unpack the sources
% cd gimp-tiny-fu-1.1.x # change to the toplevel directory
% ./configure # run the 'configure' script
% make # build GIMP
% make install # install GIMP
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.
The 'configure' script examines your system, and adapts Tiny-Fu to run
on it. The script has many options, some of which are described in the
generic instructions included at the end of this file. All of the
options can be listed using the command './configure --help'. There
are several special options the Tiny-Fu 'configure' script recognizes.
These are:
--enable-shared and --disable-shared. This option affects whether
shared libraries will be built or not. Shared libraries provide
for much smaller executables. The default is to enable shared
libraries. Disabling shared libraries is almost never a good idea.
--disable-gimp-tiny-fu-console. Use this option if you don't want the
gimp-tiny-fu-console binary to be built in addition to the standard binary.
gimp-tiny-fu-console is useful for command-line batch mode or as a server.
The 'make' command builds:
- The main Tiny-Fu program 'tiny-fu' in the 'tiny-fu' directory.
The 'make install' command installs the tiny-fu plug-in, some scripts and data
files, and language translation files. After running 'make install', and assuming
the build process was successful, you should be able to use Tiny-Fu scripts and
features when you run GIMP.
When ./configure fails
======================
'configure' uses pkg-config, a tool that replaces the old foo-config
scripts. The most recent version is available from
http://www.freedesktop.org/software/pkgconfig/
'configure' checks for the glib and gtk+ libraries on your system. In
addition to these libraries, it also checks for GIMP libraries. You need
the related libraries and header files installed, otherwise you'll get a
message that will indicate which library was not found.
If you are sure that those libraries are correctly installed, but configure
fails to detect them, the following might help:
Set your LDFLAGS environment variable to look for the library in a certain
place, e.g. if you are working in a bash shell you would say:
export LDFLAGS="-L<path_to_library> -L<path_to_another_one>"
before you run configure.
Set your CPPFLAGS environment variable to look for the header file in a
certain place, e.g. if you are working in a bash shell you would say:
export CPPFLAGS="-I<path_to_header_file> -I<path_to_another_one>"
before you run configure.
* An old version of the GTK+ libraries was found instead of
your newly installed version. This commonly happens if a
binary package of GTK+ was previously installed on your system,
and you later compiled GTK+ from source.
Fix: Remove the old libraries and include files. If you are afraid
that removing the old libraries may break other packages supplied by
your distributor, you can try installing GLib, GTK+ and other
libraries in a different prefix after setting the environment
variable PKG_CONFIG_LIBDIR to point to lib/pkgconfig/ in that new
prefix so that it does not try to read the *.pc files from the
default directory (/usr/lib/pkgconfig). However, removing the old
packages is often the easier solution.
A detailed log of the ./configure output is written to the file
config.log. This may help diagnose problems.
Generic Instructions for Building Auto-Configured Packages
==========================================================
To compile this package:
1. Configure the package for your system. In the directory that this
file is in, type './configure'. 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.
The 'configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation, and
creates the Makefile(s) (one in each subdirectory of the source
directory). In some packages it creates a C header file containing
system-dependent definitions. It also creates a file 'config.status'
that you can run in the future to recreate the current configuration.
Running 'configure' takes a minute or two.
To compile the package in a different directory from the one
containing the source code, you must use GNU make. 'cd' to the
directory where you want the object files and executables to go and
run 'configure' with the option '--srcdir=DIR', where DIR is the
directory that contains the source code. Using this option is
actually unnecessary if the source code is in the parent directory of
the one in which you are compiling; 'configure' automatically checks
for the source code in '..' if it does not find it in the current
directory.
By default, 'make install' will install the package's files in
/usr/local/bin, /usr/local/lib, /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 machine-specific
files and machine-independent files. If you give 'configure' the
option '--exec-prefix=PATH', the package will use PATH as the prefix
for installing programs and libraries. Normally, all files are
installed using the same prefix.
'configure' ignores any other arguments that you give it.
If your system requires unusual options for compilation or linking
that 'configure' doesn't know about, you can give 'configure' initial
values for some variables by setting them in the environment. In
Bourne-compatible shells, you can do that on the command line like
this:
CC='gcc -traditional' DEFS=-D_POSIX_SOURCE ./configure
The 'make' variables that you might want to override with environment
variables when running 'configure' are:
(For these variables, any value given in the environment overrides the
value that 'configure' would choose:)
CC C compiler program.
Default is 'cc', or 'gcc' if 'gcc' is in your PATH.
INSTALL Program to use to install files.
Default is 'install' if you have it, 'cp' otherwise.
INCLUDEDIR Directory for 'configure' to search for include files.
Default is /usr/include.
(For these variables, any value given in the environment is added to
the value that 'configure' chooses:)
DEFS Configuration options, in the form '-Dfoo -Dbar ...'
LIBS Libraries to link with, in the form '-lfoo -lbar ...'
If you need to do unusual things to compile the package, we encourage
you to teach 'configure' how to do them and mail the diffs to the
address given in the README so we can include them in the next
release.
2. Type 'make' to compile the package.
3. Type 'make install' to install programs, data files, and
documentation.
4. You can remove the program binaries and object files from the
source directory by typing 'make clean'. To also remove the
Makefile(s), the header file containing system-dependent definitions
(if the package uses one), and 'config.status' (all the files that
'configure' created), type 'make distclean'.
The file 'configure.in' is used as a template to create 'configure' by
a program called 'autoconf'. You will only need it if you want to
regenerate 'configure' using a newer version of 'autoconf'.
......@@ -19,8 +19,8 @@ m4_define([tiny_fu_stable],
m4_if(m4_eval(plugin_minor_version % 2), [0], [yes], [no]))
dnl required versions of other packages
m4_define([glib_required_version], [2.4.5])
m4_define([gtk_required_version], [2.4.4])
m4_define([glib_required_version], [2.10.2])
m4_define([gtk_required_version], [2.8.17])
m4_define([gimp_required_version], [2.3.10])
AC_INIT([plugin_name], [plugin_version])
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment