Hi Patrick,
……is that to say that the 'make' process will pause at this point for user input? at which point I would enter
yep, so far you've got it right. Let me explain it a bit more:
The installation script is undoubtedly somewhat 'old-fashioned', I did not spend much time on it and merely copied Gregs classic Radiance 'makeall',
and just modified it here and there. So in general it still has that queer Unix/Linux flavour ...
If you run the command 'makeall RADZILLA' from a terminal (on some OSes you may have to type ./makeall, the ./ means search in the current directory for the executable, which is in this case the script)
Ok, ehhm, yeah, if you type makeall RADZILLA the script prompts at some points for user input, answer y or n, or input of a directory name for the
exectuables etc, etc At one point right at the beginning you're asked for your favorite editor program. Type in the name of the program you normally use for simple text editing tasks. Later, e.g when the follwing questions appear
1) Edit basic compilation parameters (compiler options etc.)
2) Edit QT specific parameters (Location of QT libraries etc.)
3) Return to OS selection
4) Continue installation
you can e.g. type 2 at the prompt, then the script will call the mentioned editor and you can edit a separate file which holds
the specific info for compiling (locations of the libraries and other stuff). Here you can adjust the specific data for your OS installation.
When you close the editor you always return to the above question, and if everything is ok, you finally can type 4 to continue the installation, compiling will then start with the parameters you have changed.
This editor hack is the same as Greg uses in his classic makeall, and it makes it a lot simpler for me, as I don't have to include an editor in the script but just use one which is present on your system.
So far for the way to adjust the compiling process, I admit that I should have written some explanations also on the meaning of the variables:
normally, each QT installation is collected into some base or root directory, this is the variable
QTDIR (on my system it's /usr/lib/qt3).
For compling stuff which uses the QT libraries you need a) header files and b) the libraries itself, the headerfiles reside in the 'include-.directory'
QTINCL, that cryptic -I$(QTDIR)/include is already the format the compiling program (eg. g++) needs as input parameter, in my case it translates to
/usr/lib/qt3/include
QTLIB points to the location of the library, QTLIBNAME is another gimmick, sometimes the library is named
libqt.so, sometimes it is named libqt-mt.so (that 'lib' is always ommitted in the paramater name, again the -lqt-mt is already in the format the compiler expects.
And finally, the last special QT gimmick: QT has a so called 'meta compiler', which is just another step during the compilation, and it means a separate program called 'moc' is run which produces some additional code out of existing files. The parameter
MOC points to this program..
Ok, OK Ok, this is probably quite a lot for all who just want to run and use RADZILLA and don't want to bother half a day about all the intricacies of compiling and esp. checking where is what on different systems, but normally it is not a heavy as it sounds.
So you have to check if /Developer/qt contains a subdirectory 'include' and one named 'lib' and one named 'bin', and further if there are header files in the include-dir (tons of files with ending .h) and if there are libraries in .../lib (files named e.g libqt.so.3.3.5 and symbolic links like libqt.so or libqt.mt.so) and if there is an exectuable called 'moc in ..../bin,
If this is the case you can simply edit the QTDIR declaration to
QTDIR=/Developer/qt.
i.e you only have to edit one variable, the one poiting to the base directory of your QT installation.
If your QT installation is not in a separate base directory, then all stuff probably is simply thrown into /usr/local/lib, mixed with everything else from
other tools and programs. I would be strange but in principle its possible. To be on the safe side you then better check where the necessary files are and set each of the variable separately.
You might use the 'find' command (if it exists on MacOSX, its a standard Unix commad, so it should exist.)
As an example, you can type:
find /usr -name moc
this looks for the program moc , starting from /usr and all its subdirectories. You might get something like
/usr/local/bin/moc or
/usr/lib/qt3/bin/moc
as result, whatever the result is, this is the name you have to set for the varable MOC when editing the compiling parameters during the makeall run ...
Hope this helps ..
-Carsten
···
--
---------------------------------------------------------
"Der Deckel muß zugehen." (P.Kölsch)
---------------------------------------------------------