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

[bruce]

hi..

while this would/could work.. is it the accepted way??? or simply a kludge?

thanks.


-----Original Message-----
From: Reuben D. Budiardja [mailto:techlist at voyager.phys.utk.edu]
Sent: Wednesday, September 08, 2004 5:23 AM
To: bedouglas at earthlink.net; General Red Hat Linux discussion list
Subject: Re: using options for './configure' for software builds..


On Wednesday 08 September 2004 07:51, bruce wrote:
<snip>
> ie, instead of doing:
>   ./configure --option1 --option2....
>   ./configure option_file
>
> option_file
>   --option1
>   --option2
>   .
>   .
>   .
>
> in this case option_file would have the optins....
>
> so how does this get accomplished under linux???
>
> i'm sure there's a way to not have to continue to retype the options, i
> just need to know what the correct way is!

How about put the whole thing into a script, then run that script instead of
the original ./configure, ie (not tested):

1. Edit: my_configure.sh

#! /bin/sh
./configure \
--option1 \
--option2 \
--option3

2. Make my_configure.sh executable
chmod 755 my_configure.sh

3. Run my_configure.sh instead of the original configure script;
./my_configure.sh

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------