Re: FVWM: Gnu configure on next realease ???

From: Barry A. Warsaw <bwarsaw_at_newcnri.cnri.reston.va.us>
Date: Thu, 23 May 1996 10:42:51 -0400

>>>>> "JL" == Jean-Marc Lasgouttes <Jean-Marc.Lasgouttes_at_inria.fr> writes:

    JL> I agree completely with Anthony. One more point in favor of
    JL> autoconf. Since you write the skeleton of the Makefile(s), it
    JL> is by design human readable. This means that, unlike
    JL> imake-generated Makefiles, you can hack them if something goes
    JL> wrong.

    JL> Concerning setting up correctly imake, it can be very
    JL> difficult to do on some proprietary systems and versions of
    JL> X11. It is better to fix fvwm once than to tell a bunch of
    JL> people to fix their setup.

The thing to do is leave the system config files in place, make a copy
of the config directory into someplace you can edit, then also copy
xmkmf (it's just a script, at least under OpenWindows) so that it uses
the new config files by default. Then make sure your xmkmf is earlier
in your path.

But you are definitely right that imake config files, and the
generated Makefiles are not humanly readable. :-) Hacking those
config files is a major pain.

-Barry
--
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 - 11:32:31 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:59 BST