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

From: Todd Fries <todd_at_miango.com>
Date: Thu, 23 May 1996 14:34:24 -0500 (CDT)

> grossjoh> ./configure --with-x\
> grossjoh> --x-includes=/usr/local/X11R6/include\
> grossjoh> --x-libs=/usr/local/X11R6/lib
> I think it is too tired :-) Editing *akefile and execute appropriate
> command of what you want. It's simple :-)
>
> Somebody says GNU configure is flexible because of command-line
> option, but it's unflexible because of command-line ONLY. Editing
> *akefile after 'sh ./configure' is out of the questions :-)
>
> Using GNU configure as a default is easy. But it's less
> flexible when we want to use 'site specific' setup.

Oh really? Then what the heck do you call that? Non-site-specific?

Personally, I am setting up a set of makefiles that when I type
'make packagename' it will download, uncompress, compile, and install
stuff without a single other lift of the finger.

I know, I'm lazy, but hey, isn't that was make is for?

Anyway, I have found it tons easier to give configure command line options
for where I want to install stuff. Things done with imake I have had
to edit makefiles per application, figure out where it's install
prefix is if there is such a beast in a variable, and perhaps supply my
auto-mated compiler with a patch for the makefile if there isn't.

To me it is tons easier to just do:

./configure --prefix=/abc/software/fvwm-2.0.42/Linux

and then

./configure --prefix=/abc/software/fvwm-2.0.42/solaris

rather than:

cd /abc/software/fvwm-2.0.42/Linux/src/fvwm-2.0.42
patch -p1 < /abc/software/fvwm.linux.patch
MakeMakefiles

and then

cd /abc/software/fvwm-2.0.42/solaris/src/fvwm-2.0.42
patch -p1 < /abc/software/fvwm.solaris.patch
MakeMakefiles

And pray that nobody changes the Fvwm.tmpl file, so I don't have
to manually redo the patches.

I think it is becoming quite clear what is an easier solution.
-- 
Todd Fries .. todd_at_miango.com .. todd_at_emcee.com .. tfries_at_umr.edu
--
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 - 16:27:05 BST

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