Table of Contents
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
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
If you need to do unusual things to compile the package, please try
to configure 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
contains results you don't want to keep, you may remove or edit it.
configure.in is used to create
configure by a program
autoconf. You only need “configure.in” if you want to change
it or regenerate
configure using a newer version of
The simplest way to compile this package is:
cd to the directory containing the package's source code and type
./configure to configure the package for your system. If you're
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. To know all of the possible options, type
or read the next section about options.
configure takes awhile. While running, it prints some
messages telling which features it is checking for.
make to compile the package.
make check to run any self-tests that come with
make install to install the programs, data files and
You can remove the program binaries and object files from the
source code directory by typing
make clean. To also remove the
configure created (so you can compile the package for
a different kind of computer), type
make distclean. There is
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.
If you don't find the
configure shell, you have to generate it with
gen-conf.sh. The processing using the GNU build sytem gives a
QTDIR is properly set :
QTDIR/bin should contain moc, qtconfig... ,
QTDIR/lib the libs and
QTDIR/include the Qt headers ...
To compile the documentations, type
make html and
make install to install the documentation the
In this section, you can find the most used options. To know all of the possible options, type
The value is the path where you want to install Tulip.
bin, include, lib directories was created in this location. By default, it is
Add compilation flags to allow debugging.
Enable make rules and dependencies not useful (and sometimes confusing) to the casual installer. For example, if you modify a
Makefile.am file, it is detected and the
Makefile is updated.
Enable to specify special tags for the g++ compiler. It is an important part to have great performings. For example, you can specify the architecture of your PC : --CXXFLAGS="-DNDEBUG -O3 --funroll-loops
-mtune=pentium4 -narch=pentium4 -pipe". For more informations about the options of compilations for g++, see the web site of gcc, here.