>>>>> " " == =?ISO-2022-JP?B?GyRCJF4kRCQ3JD8kXiQzJEgbKEI=?= <ISO-2022-JP> writes:
amartin> This is why configure takes the options --x-includes=DIR
amartin> and --x-libraries=DIR so that you can manually override
amartin> configure.
> I want configure to detect which X is used by automatically :-)
Well, it takes the xmkmf which is the first on the path. This is a
good way to find the good X.
> Well, the point that I want NOT to use GNU autoconf is "Writing
> appropriate configure.in and/or related stuff (to make
> configure configure script) is difficult than writing
> appropriate Imakefile". I want NOT to force all developer who
> want to contribute/write a module for fvwm.
Once the main configure script is written, it can generated a file
Make.rules which contains all the variables parts of the setup. Then
the developper of a module only has to write a module containing a few
lines (mostly the list of object files...).
> Though configure script is maybe flexible and usable, why only
> a few application (except the GNU product) uses GNU autoconf
> for generating ? I think many developer want NOT to use GNU
> autoconf because of difficulty...
Well, X applications use imake because we were told it is the right
thing to do. However, I maintain a configure script for an X
application (LyX, a word processor written in C++) and it works well.
Jean-Marc
--
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 Fri May 24 1996 - 04:21:06 BST