using options for './configure' for software builds..

[Reuben D. Budiardja]

On Wednesday 08 September 2004 08:57, bruce wrote:
> hi..
>
> while this would/could work.. is it the accepted way??? or simply a kludge?

What do you mean "the accepted way"? It's one way, and different people will 
come up with different solutions.
Usually you only run configure once, then 'make' and 'make install'. That's 
why no one bother to come up with some sort of standardization to put 
configure options to a file. 
I have, however, found a situation where I need to play around with configure 
options, and 'make' the source code many times. In that situation, what I 
proposed was what I did.

For me, It worked, therefore it's acceptable, at least in most cases this is 
trivial thing. If you're talking about configuration for linux kernel, then 
it's no longer trivial. :)

RDB
-- 
Reuben D. Budiardja
Dept. Physics and Astronomy
University of Tennesse, Knoxville, TN

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GIT/M/MU/P/S d-(++) s: a-- C++(+++) UL++++ P-- L+++>++++ E- W+++ 
N+ o? K- w--- !O M- V? !PS !PE Y PGP- t+ 5 X R- tv+ 
b++>+++ DI D(+) G e++>++++ h+(*) r++ y->++++
------END GEEK CODE BLOCK------