Recent Changes - Search:

PmWiki

pmwiki.org

edit SideBar

Tina6ConfigureFlags

Configure Options for TINA 6

General Comments

In order to compile Tina 6, download the tina-libs and tina-tools tarballs to a convenient directory (e.g. /usr/local/Tina6), unzip and untar both using

tar -xvf tina-libs-tarball-name.tar.gz
tar -xvf tina-tools-tarball-name.tar.gz

cd into the tina-libs directory created during the above step and use

./configure
make
make install

then cd into the tina-tools directory and repeat. The libraries will be installed in the libs subdirectories of the tina-libs and tina-tools directories, and a sample toolkit (TINA executable) will be installed in the bin subdirectory of the tina-tools directory.

There are no TINA-specific options for the configure script in the tina-libs area. However, the configure script in the tina-tools area needs to find the tina-libs libraries and header files, and the Gtk libraries and header files. If the automated searches for these fail, then locations can be specified manually using the options described on this page.

Multi-Core Processors

If your machine has a multi-core processor (most modern machines do) then you can considerably increase the speed of the build by utilizing all available cores. In order to do this, use the -j flag for the make command e.g.

make -j 4

will allow make to use up to four parallel threads. From some brief experimentation, it seems that setting the number to twice the number of available cores provides the best results.

C Flags

If you want to compile the tina-libs and tina-tools code with specific flags, such as the optimisation flag for the C-compiler, then all you have to do is give arguments to the ./configure command.

eg, if you wanted to compile with an -O2 flag, then write:

./configure CFLAGS=-O2

Basically, any environment variable can be specified this way. If you need to specify more than one flag, enclose them in double quotes e.g.

./configure CFLAGS="-g -O2"

Endianness

If you find that TINA hangs when reading in DICOM images, you probably need to specify which Endian Architecture your machine is. The default for TINA is to assume that DICOM images will be Little Endian Explicit (I think), therefore when presented with Little Endian Implicit, doesn't know what to do.

If you are on a Linux platform, please use:

./configure CFLAGS=-DLITTLE_ENDIAN_ARCHITECTURE

To be on the safe side, if you are using SunOS?, please use:

./configure CFLAGS=-DBIG_ENDIAN_ARCHITECTURE

Tina Libraries And Headers

At the end of the output from configure.sh in the tina-tools area is a report on the library locations that have been found via the automatic search. If required libraries are not found, warning messages will be given.

The tina-libs libraries and headers should be found if they are in a directory alongside the tina-tools directory. If they are not found, then their locations can be specified using

./configure --with-tina-includes=/path/tina-libs --with-tina-libraries=/path/tina-libs/lib

where path is the pathname of the directory where you untarred the tarballs (e.g. /usr/local/Tina6).

Gtk+ 2 Library Locations

Tina 6 uses pkg-config to find your Gtk+ 2 installation, and so failure to find it implies that it is not installed. However, if you are sure that you have installed Gtk+ 2 but it is not found, you can specify the location manually using

./configure --with-gtk-prefix=/path/to/gtk.h

Piping Errors To A Text File

Gcc has two output streams: the first is used for general messages, the second for warnings and errors. Usually both go to standard output (the terminal) but it can be useful to pipe the errors and warnings to a text file, without the general messages, so that they can be read more easily. I haven't found a way to do this using bash, but you can use

sh -c 'make 2>errors.txt'

instead. This sends the first output stream to the terminal, and the warnings and errors to errors.txt. (Those are apostrophes i.e. the symbol on the @ key on a UK keyboard, not grave accents i.e. the symbol on the key under the Esc key). Note that the text file must not exists before typing this command.

Edit - History - Print - Recent Changes - Search
Page last modified on March 05, 2012, at 06:39 PM