bug#13524: Improving user experience for non-recursive builds

>> Hmm, if that's the case, then I think "canon" is the wrong term to >> use, as it typically implies that the result is still in the same >> domain as the input. >> > Suggestions for a better name then? Dunno... something like "RELDIR_SYM" would make sense ... it's a symbol corresponding to RELD

bug#13524: Improving user experience for non-recursive builds

On 02/07/2013 10:52 AM, Miles Bader wrote: >>> ... and "canon_reldir" means the same thing, except canonicalized? >>> >> Yes, "canonicalized" in a sense quite specific to Automake: >> >> >> >> >> So, for example, if %re

bug#13524: Improving user experience for non-recursive builds

>> ... and "canon_reldir" means the same thing, except canonicalized? >> > Yes, "canonicalized" in a sense quite specific to Automake: > > > > So, for example, if %reldir% expands to 'foo/bar-baz.d', '%canon-reldir%' > w

bug#13524: Improving user experience for non-recursive builds

On 02/05/2013 02:01 AM, Miles Bader wrote: > %...% seems nice to me. > I'm fine to settle for that (see my reply to last mail from Peter for more details). > Incidentally, given the name, I assume the name "reldir" always refers > to a relative path? What is it relative to again? > The path of th

bug#13524: Improving user experience for non-recursive builds

On 02/05/2013 12:03 AM, Peter Rosin wrote: > On 2013-02-04 19:11, Stefano Lattarini wrote: >> On 02/04/2013 06:33 PM, Eric Blake wrote: >>> So they aren't quite affected by configure, but they are dependent on >>> relative location, just like existing substitutions like @top_srcdir@ >>> are depende