amartin> Imake doesn't know all about the development environment.
If your imake doesn't know all about the development environment,
that's the misconfiguration of imake :-) Imake SHOULD know the environment.
amartin> After all, everyone buys a commercial compiler from the OS
amartin> vendor rather than using GCC, right? :-)
Hmm :-) Then, everyone gets X11R6 distribution and make their own X if
they can, right? :-)
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 ?
***
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).
It should be included to step 2) ?
2) do './configure'.
Configure makes Imakefile, and do 'xmkmf', 'make Makefiles',
and so on ('xmkmf -a' is enough ?).
3) do 'make'.
**/Makefile is already generated by imake.
4) do 'make install'
Wow, it's happy :-)
Any comments ?
- -
Makoto `MAR_kun' MATSUSHITA
--
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 - 01:22:46 BST