Re: About dynamic configure options.

2012-12-14 Thread Eduardo Costa
Hi Stefano, Sorry then!, I was a bit in a hurry yesterday. So they can have an idea then. Thanks, On 14/12/2012, Stefano Lattarini wrote: > On 12/13/2012 11:22 PM, Eduardo Costa wrote: >> Thanks guys, >> >> I actually sent a "solution" much like yours Nick. Don't know >> why Stefano didn't se

Re: About dynamic configure options.

2012-12-14 Thread Stefano Lattarini
On 12/13/2012 11:22 PM, Eduardo Costa wrote: > Thanks guys, > > I actually sent a "solution" much like yours Nick. Don't know > why Stefano didn't send my answer. > You mean this part? This might be done by usual means (couldn't do it) or just with some trickery to to inject the string manual

Re: About dynamic configure options.

2012-12-13 Thread Eduardo Costa
Thanks guys, I actually sent a "solution" much like yours Nick. Don't know why Stefano didn't send my answer. This is what I came up with: AC_DEFUN([TRICK], [m4_divert_text([HELP_CANON], [_ACEOF echo -en "\n* --option=VALDate: `date`" cat <<\_ACEOF])]) TRICK You can see automake's a

Re: About dynamic configure options.

2012-12-13 Thread Nick Bowler
On 2012-12-13 10:20 -0700, Eric Blake wrote: > On 12/13/2012 05:58 AM, Stefano Lattarini wrote: > > On 12/11/2012 12:57 AM, Eduardo Costa wrote: > >> Is it possible at all to have a configure option whose help message can > >> expand a > >> variable, or can otherwise accept the output of a command

Re: About dynamic configure options.

2012-12-13 Thread Eric Blake
On 12/13/2012 05:58 AM, Stefano Lattarini wrote: > Hi Eduardo. > > On 12/11/2012 12:57 AM, Eduardo Costa wrote: >> Hi, >> >> Is it possible at all to have a configure option whose help message can >> expand a >> variable, or can otherwise accept the output of a command at configure-time? >> >> Fo

Re: About dynamic configure options.

2012-12-13 Thread Stefano Lattarini
Hi Eduardo. On 12/11/2012 12:57 AM, Eduardo Costa wrote: > Hi, > > Is it possible at all to have a configure option whose help message can > expand a > variable, or can otherwise accept the output of a command at configure-time? > > For example, imagine this as part of the output of `./configur

Re: Setting external directory in ./configure --options

2011-03-03 Thread Eric Blake
On 03/03/2011 10:25 AM, Xochitl Lunde wrote: > What I most want is something like: ./configure -ospath=/cygdrive/c/path Using that spelling would violate GNU Coding Standards, but this would work instead: ./configure --with-ospath=/cygdrive/c/path using AC_ARG_WITH to set up the --with-ospath pa

Setting external directory in ./configure --options

2011-03-03 Thread Xochitl Lunde
I'm not having any luck finding this in the autoconf manual. I need to compile and link in my embedded OS, but I want to choose the top-level path to the OS because I have different versions. The embedded OS has its own make system that does not use autoconf. (So I wouldn't use AC_CONFIG_SUBD

Re: configure options for directory variables in standards.texi

2008-02-12 Thread Karl Berry
Using $(FOO) [or ${FOO} - same] allows the user to override FOO when invoking make. Sure. My question was about recommending $(...) for Automake users instead of ${...}. Let's take an example. Here's one of the descriptions as it is written now: `bindir' The directory for

Re: configure options for directory variables in standards.texi

2008-02-12 Thread Bernd Jendrissek
On Feb 12, 2008 2:11 AM, Karl Berry <[EMAIL PROTECTED]> wrote: > and that, if the user not only uses Autoconf but also Automake, she > can write it as $(foodir) rather than @[EMAIL PROTECTED] > > Doesn't this practice contradict the recommendation of using ${...}? > And, although I knew thi

Re: configure options for directory variables in standards.texi

2008-02-11 Thread Karl Berry
Hi Ralf, I wonder whether all the indirection references ("This should normally Those are the main things I was wondering about. be `foodir' but write it as `$(bardir)/foo', and with Autoconf, as @foodir@) should be changed to the effect that ${bardir}/foo is recommended as a con

Re: configure options for directory variables in standards.texi

2008-02-10 Thread Ralf Wildenhues
Hello Karl, * Karl Berry wrote on Mon, Feb 11, 2008 at 12:51:36AM CET: > > I'd like to ask rms to approve having all the configure options that set > the directory variables (prefix, bindir, ...) in standards.texi. So > that people who don't use autoconf know that they

configure options for directory variables in standards.texi

2008-02-10 Thread Karl Berry
Hi, I'd like to ask rms to approve having all the configure options that set the directory variables (prefix, bindir, ...) in standards.texi. So that people who don't use autoconf know that they need to be implemented. Apparently rms had some objection to --prefix when it was first i

Re: defining configure options...

2006-09-27 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ben Bergen on 9/27/2006 9:40 PM: > Does anyone know if it's possbile to define a configure option like > --cell-prefix="..." instead of --with or --enable? Possible? Perhaps. Recommended? No. It is a deliberate design decision of the

defining configure options...

2006-09-27 Thread Ben Bergen
Does anyone know if it's possbile to define a configure option like --cell-prefix="..." instead of --with or --enable? -- Benjamin Karl Bergen CCS-2 Continuum Dynamics Los Alamos National Laboratory ___ Autoconf mailing list Autoconf@gnu.org htt

Re: how to define my own configure options

2006-04-04 Thread Noah Misch
On Tue, Apr 04, 2006 at 02:15:12PM +0200, Harald Dunkel wrote: > What is the recommended procedure to define my own configure > options in configure.ac, e.g. "--report" to list the settings > found, or "--shorthelp" to list just the "non-standard" options, &g

Re: how to define my own configure options

2006-04-04 Thread Ralf Corsepius
On Tue, 2006-04-04 at 14:15 +0200, Harald Dunkel wrote: > What is the recommended procedure to define my own configure > options in configure.ac, e.g. "--report" to list the settings > found, or "--shorthelp" to list just the "non-standard" options, autoc

how to define my own configure options

2006-04-04 Thread Harald Dunkel
Hi folks, I haven't seen it mentioned anywhere, so hopefully you don't mind me asking? What is the recommended procedure to define my own configure options in configure.ac, e.g. "--report" to list the settings found, or "--shorthelp" to list just the "non-stand

Re: enable/disable configure options for subpackages

2005-07-27 Thread Bob Rossi
> > On Fri, Jul 15, 2005 at 12:14:44PM +0200, Stepan Kasal wrote: > > > Of course some hacks are possible: > > > 1) fiddle with ac_args before AC_OUTPUT. > > >Of course this solution may easily break with future versions of > > > autoconf. > > > > > > 2) Read what AC_CONFIG_SUBDIRS does (how

Re: enable/disable configure options for subpackages

2005-07-27 Thread Stepan Kasal
Hello, On Tue, Jul 26, 2005 at 08:55:30PM -0400, Bob Rossi wrote: > Does autoconf > only pass the explicit arguments down to the lower confurations? or if I > have a --enable-shared=no defaulted option, would that work? it passes the options as they were given on the cmdline. So if you don't give

Re: enable/disable configure options for subpackages

2005-07-26 Thread Bob Rossi
On Fri, Jul 15, 2005 at 12:14:44PM +0200, Stepan Kasal wrote: > Hello, > > On Thu, Jul 14, 2005 at 03:36:48PM -0400, Bob Rossi wrote: > > > > Is there a way to pass in --disable-shared to the AC_CONFIG_SUBDIRS? > > I apologize for the wrong answer I gave previously. > > No, I don't know about an

Re: enable/disable configure options for subpackages

2005-07-15 Thread Stepan Kasal
Hello, On Thu, Jul 14, 2005 at 03:36:48PM -0400, Bob Rossi wrote: > > > Is there a way to pass in --disable-shared to the AC_CONFIG_SUBDIRS? I apologize for the wrong answer I gave previously. No, I don't know about any such solution. Of course some hacks are possible: 1) fiddle with ac_args be

Re: enable/disable configure options for subpackages

2005-07-14 Thread Bob Rossi
On Thu, Jul 14, 2005 at 04:57:06PM +0200, Stepan Kasal wrote: > Hello, > > On Thu, Jul 14, 2005 at 09:50:08AM -0400, Bob Rossi wrote: > > Is there a way to pass in --disable-shared to the AC_CONFIG_SUBDIRS? > > I looked into the source (status.m4, general.m4), and it seems that all > --enable-*

Re: enable/disable configure options for subpackages

2005-07-14 Thread Bob Friesenhahn
subconfigures. Thus --disable-shared should be propagated automatically. Have you tried it? He is trying to build one subdirectory using different configure options from the others. With your advice, --disable-shared would be provided to the whole build, so that shared libraries can'

Re: enable/disable configure options for subpackages

2005-07-14 Thread Stepan Kasal
Hello, On Thu, Jul 14, 2005 at 09:50:08AM -0400, Bob Rossi wrote: > Is there a way to pass in --disable-shared to the AC_CONFIG_SUBDIRS? I looked into the source (status.m4, general.m4), and it seems that all --enable-* arguments are propagated to the subconfigures. Thus --disable-shared should

Re: enable/disable configure options for subpackages

2005-07-14 Thread Bob Friesenhahn
On Thu, 14 Jul 2005, Bob Rossi wrote: I already use, AC_CONFIG_SUBDIRS to configure the readline subpackage. However, by default the readline library builds both shared and static libraries. --enable-shared build shared libraries [default=YES] --enable-static build static libra

enable/disable configure options for subpackages

2005-07-14 Thread Bob Rossi
Hi, Sorry for all the questions lately, it's just, some of them I don't see an easy answer for in the manual. If there is an easy answer to this question, maybe I'll append a small example to the manual. I already use, AC_CONFIG_SUBDIRS to configure the readline subpackage. However, by default th

Re: passing configure options via AC_CONFIG_SUBDIRS

2001-08-15 Thread Ralf Corsepius
Am 15 Aug 2001 09:44:00 -0500 schrieb Paul Martinolich: > Sorry, I was unclean. I'll give it another shot. I have this structure > > ../src > ../pkgA > ../pkgB > > src contains my application. Platform A does not provide the third party > pkgA which I need in the application, whereas Pl

Re: passing configure options via AC_CONFIG_SUBDIRS

2001-08-15 Thread Paul Martinolich
Sorry, I was unclean. I'll give it another shot. I have this structure ../src ../pkgA ../pkgB src contains my application. Platform A does not provide the third party pkgA which I need in the application, whereas Platform B does. Ditto for pkgB. Some platforms provide it and others do

Re: passing configure options via AC_CONFIG_SUBDIRS

2001-08-15 Thread Akim Demaille
>>>>> "Paul" == Paul Martinolich <[EMAIL PROTECTED]> writes: Paul> I have a configure.ac in which I conditionally configure Paul> additional sources that have their own ./configure scripts. Paul> Using AC_CONFIG_SUBDIRS works great. But, now I'd lik

passing configure options via AC_CONFIG_SUBDIRS

2001-08-14 Thread Paul Martinolich
I have a configure.ac in which I conditionally configure additional sources that have their own ./configure scripts. Using AC_CONFIG_SUBDIRS works great. But, now I'd like to pass some configure options that I don't use in my top-level configure. How can I pass these to the

Re: custom configure options

2001-07-11 Thread Tim Van Holder
> configure --omfdirs=/opt/share/omf:/usr/share/omf > > I couldn't figure out from the docs how to do it. The AC_ARG_ENABLE > macro looked the closest, but I don't think it is the right one. Or do I > have to write a macro for this? Indeed, ARG_ENABLE is not the right one for this type of option

custom configure options

2001-07-10 Thread László Kovács
Hi, I am trying to add some custom options to my configure file. Something like: configure --omfdirs=/opt/share/omf:/usr/share/omf I couldn't figure out from the docs how to do it. The AC_ARG_ENABLE macro looked the closest, but I don't think it is the right one. Or do I have to write a macro f

Re: configure options

2000-11-22 Thread Lars Hecking
> I'm working on a project with a pretty large (and increasing) > number of configure parameters, so I look for ways to store sets > of parameters externally, such that they be used much like config.cache, > if desired. Since all possible arguments could be known from the macros > used in config

configure options

2000-11-22 Thread Stefan Seefeld
Hi, I'm working on a project with a pretty large (and increasing) number of configure parameters, so I look for ways to store sets of parameters externally, such that they be used much like config.cache, if desired. Since all possible arguments could be known from the macros used in configure.in,