Hello,
On Wed, Jun 08, 2005 at 08:49:37PM +0200, Alexandre Duret-Lutz wrote:
> Stepan> Do you think it should be reported by AC_SUBST_TRACE, too?
>
> Either way is fine with me.
I committed the patch attached to this mail.
Stepan
2005-06-29 Stepan Kasal <[EMAIL PROTECTED]>
* lib/aut
>>> "Stepan" == Stepan Kasal <[EMAIL PROTECTED]> writes:
[...]
Stepan> Actually, I'm considering the possibility to make one exception
Stepan> on Autoconf side: @configure_input@ is a strange substitution.
Stepan> Do you think it should be reported by AC_SUBST_TRACE, too?
Either way is fine w
Hi,
On Tue, May 24, 2005 at 06:22:45PM +0200, Alexandre Duret-Lutz wrote:
> Stepan> OK. Alexandre, I'm new to this, could you please
> Stepan> suggest a name for the macro?
>
> I'm not good at naming things. AC_SUBST_TRACE (like
> AC_DEFINE_TRACE) or AC_OUTPUT_VARIABLE ?
OK, it'll be AC_SUBS
>>> "Stepan" == Stepan Kasal <[EMAIL PROTECTED]> writes:
Stepan> Hello,
Stepan> On Wed, May 18, 2005 at 11:04:04AM +0200, Alexandre Duret-Lutz wrote:
Stepan> Or perhaps you could trace a different macro, not directly AC_SUBST.
>>
>> That sounds the right thing to do to me.
Stepan> OK. Ale
Hello,
On Wed, May 18, 2005 at 11:04:04AM +0200, Alexandre Duret-Lutz wrote:
> Stepan> Or perhaps you could trace a different macro, not directly AC_SUBST.
>
> That sounds the right thing to do to me.
OK. Alexandre, I'm new to this, could you please suggest a name for the
macro?
> I'd rather
>>> "Stepan" == Stepan Kasal <[EMAIL PROTECTED]> writes:
[...]
Stepan> Yes, I could use an m4_if inside AC_SUBST to handle them specially.
That means maintaining a list of variables far from their definitions.
Stepan> Or perhaps you could trace a different macro, not directly AC_SUBST.
That
Hello,
On Sat, May 14, 2005 at 05:24:11PM +0100, Keith Marshall wrote:
> > Stepan> abs_srcdir
> > Stepan> abs_builddir
> > Stepan> abs_top_srcdir
> > Stepan> abs_top_builddir
...
> Doesn't autoconf already AC_SUBST these?
no, it doesn't. The variables are substituted, but it's not achieved
On Saturday 14 May 2005 4:10 pm, Alexandre Duret-Lutz wrote:
> >>> "Stepan" == Stepan Kasal <[EMAIL PROTECTED]> writes:
>
> [...]
>
> Stepan> I suggest that Automake automatically sets these make variables:
>
> Stepan> abs_srcdir
> Stepan> abs_builddir
> Stepan> abs_top_srcdir
> Stepan> abs_to
>>> "Stepan" == Stepan Kasal <[EMAIL PROTECTED]> writes:
[...]
Stepan> I suggest that Automake automatically sets these make variables:
Stepan> abs_srcdir
Stepan> abs_builddir
Stepan> abs_top_srcdir
Stepan> abs_top_builddir
Why not AC_SUBST these variables in Autoconf ? Let's work on
solu
Hi,
On Wed, May 11, 2005 at 12:09:11PM +0200, Harald Dunkel wrote:
> It was easier to patch header-vars.am. See below.
> builddir is not set, so I skipped top_builddir, too.
you mean abs_builddir, I guess.
I don't think it should be skipped. Alexandre refused to add builddir
because you have to
Stepan Kasal wrote:
> Hello,
>
> On Mon, May 09, 2005 at 06:02:24PM +0200, Harald Dunkel wrote:
>
>>I tried to replace $(top_builddir)
>>in a Makefile.am by $(abs_top_builddir), but the new
>>Makefile did not define this macro.
>
>
> Actually, this is a bug/feature of Automake, that these varia
Hello,
On Mon, May 09, 2005 at 06:02:24PM +0200, Harald Dunkel wrote:
> I tried to replace $(top_builddir)
> in a Makefile.am by $(abs_top_builddir), but the new
> Makefile did not define this macro.
Actually, this is a bug/feature of Automake, that these variables
are not propagated by default.
12 matches
Mail list logo
