>
> amartin> Autoconf uses Imake if it is available to find relevent
> amartin> information such as locations of libraries and include files
> amartin> and the names of any special libraries that might be needed,
>
> Sorry I'm not familiar with autoconf, Does autoconf uses the
> informaiton of $XTOP/lib/config ? or simply kicks imake to use ?
The configure script generated by autoconf creates a very simple Imakefile
and then it runs xmkmf and looks at the generated Makefile to get the
following variables (these are on my linux system, they will differ):
ac_im_incroot="/usr/X11R6/include";
ac_im_usrlibdir="/usr/X11R6/lib";
ac_im_libdir="/usr/X11R6/lib/X11"
Then it isn't so foolish to assume that these are the actual locations, it
checks to make sure. If these aren't the correct locations, then it
continues to look in a bunch of common places to find the real libraries
and includes.
> Maybe the best (ie, easy, reliable, and portable) procedure of fvwm
> compilation is:
>
> 1) Edit configulation file to specify the features (XPM and so on).
This can be done on the command line with autoconf. i.e.
./configure --with-xpm
It can also optionally be done manually in configure.h
> 2) do './configure'.
> Configure makes Imakefile, and do 'xmkmf', 'make Makefiles',
> and so on ('xmkmf -a' is enough ?).
Just have configure make the Makefiles. Imake shouldn't be needed.
> 3) do 'make'.
> 4) do 'make install'
I have had plenty of problems trying to get Imake to work properly on
commercial Unixes (Solaris and HPUX) where it is the goal of the OS vendor
to force you to buy their development environment. HPUX doesn't even come
with Imake, and once you find it and install it, it is set up to use HP's
compiler (which isn't included) and it sets up the CFLAGS with a bunch of
non-standard compiler switches. At least Solaris comes with Imake, but
again it is set up for the commercial compiler.
I have had varying degrees of success with using options to imake i.e.
something like:
imake -DHASGCC=YES
(I don't remember the exact syntax) but nothing compares to a well-written
autoconf setup.
Tony.
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Thu May 23 1996 - 03:21:01 BST