Bernd Lachner <[EMAIL PROTECTED]> writes:
> Ok. But I don't know if I understand this right. Is it possible to give
> AC_ARG_ENABLE more than two arguments to choose. That means in configure the
> following should be possible:
>
> configure --enable-device=devicea
> or
> configure --enable-devic
Bernd Lachner <[EMAIL PROTECTED]> writes:
> Hi,
>
> thank you for your help, but now I have some more questions.
>
>> >
>> > I need some optional arguments for a configure script. I have seen the
>> > macros AC_ARG_WITH and AC_ARG_ENABLE in the autoconf manual. As far I can
>> > see, I can add ar
Bernd Lachner <[EMAIL PROTECTED]> writes:
> I want more this two types of arguments for the configure script:
>
> 1)
> --device=x where x can be devicea, deviceb,
>
> This should lead for example to a #define devicea in config.h.
>
> 2)
> --devicexresoluton=x
> --deviceyresolution=y
>
> or ev
> > 2)
> > --devicexresoluton=x
> > --deviceyresolution=y
> >
> > or even better
> >
> > --deviceres=x*y
> >
> > where x and y is an integer value. This should lead for example to a
> > #define xres 320 and #define yres 240 in config.h.
>
> Are you really sure that it's best to define these at conf
On Wed, Jun 08, 2005 at 01:19:04PM -0500, Mike Davis wrote:
> The Cray XT3 compiler drivers pass options containing quoted strings to the
> PGI compilers, specifically for the case of -L and -l options. These single-
> quotes are being picked up by 'configure' scripts, which then pass options
> wi
On 2005-05-20, at_top_builddir, a variable `configure' passes to `testsuite' via
`atconfig', changed names to at_top_build_prefix. Consequently, `configure'
generated by `autoconf' predating the change do not properly configure
`testsuite' generated by `autom4te' postdating the change, and vice-ve
