* Peter Johansson wrote on Tue, Jan 26, 2010 at 06:38:44AM CET:
> On 1/26/10 12:09 AM, Ralf Wildenhues wrote:
> >I assume you want $wanted_value to expand to either enabled or disabled?
> >Well, that cannot work: in the generated configure script, the --help
> >text comes before the code that actua
Hello Ralf, Vincent,
On 1/26/10 12:09 AM, Ralf Wildenhues wrote:
I assume you want $wanted_value to expand to either enabled or disabled?
Well, that cannot work: in the generated configure script, the --help
text comes before the code that actually deals with the command line
arguments.
Also
Hello Jeff,
* Daily, Jeff A wrote on Mon, Jan 25, 2010 at 08:27:54PM CET:
> I was curious whether there was a way to add some documentation to the
> configure --help output. An extra paragraph perhaps, near the bottom.
Yes there is, but not in a documented way (so it might break with a
future Au
Hello Vincent,
* Vincent Torri wrote on Tue, Jan 26, 2010 at 01:00:22AM CET:
> i would like to use AS_HELP_STRING in an m4 macro such that the
> description of the help is different according to the value of one
> parameter. The macro is the following:
>
> dnl use: ECORE_CHECK_MODULE(Foo, default
I was curious whether there was a way to add some documentation to the
configure --help output. An extra paragraph perhaps, near the bottom. Yes, a
README could do just as well, but I have my reasons. Thanks.
__
Jeff Daily
Scientist
Pacific North
Hey,
i would like to use AS_HELP_STRING in an m4 macro such that the
description of the help is different according to the value of one
parameter. The macro is the following:
dnl use: ECORE_CHECK_MODULE(Foo, default-enabled[, dependancy[,
ACTION-IF-FOUND[, ACTION-IF-NOT-FOUND]]])
AC_DEFUN([
Hi
I while ago I posted to the libtool list [1,2] regarding a problem I
was having with a autotools based project and the condor workflow
management system [3]. With the help of Ralf and the Condor developers
a workaround, and more importantly a solution, was found. When
compiling code for use wit
