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. For example if you wanted to compile with an -O2 flag, then write:
Basically, any environment variable can be specified this way.
If you find that Tina5 hangs when reading in DICOM images, you probably need to specify which Endian Architecture your machine is. The default for Tina5 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:
To be on the safe side, if you are using SunOS, please use:
Gtk Library Locations
On Suse 9.1 the Gtk libraries are located in /opt/gnome: this differs from the location in previous version of Suse, with the result that our m4 scripts no longer find them. For now, specify the Gtk location by hand using
or use tina5_simple_build.sh in your tina-libs directory: the file contains comments describing how.
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 exist before typing this command.