On Fri, 9 Oct 2020 at 16:46, Cristian Morales Vega
wrote:
> There is any way to obtain the path of one directory relative to
> another in automake without adding a new dependency? "realpath"
> implemented as a m4 macro, maybe?
After I did stop focusing on automake and looked at autoconf for a
mom
suggests that it can be scripted in portable shell (
So it seems, although:
current="${2:+"$1"}"
target="${2:-"$1"}"
... etc...
all these myriad fancy variable substitutions would have to be replaced
with sed, or something ... --thanks, karl.
I would use or copy the definition in GNU Autoconf. Portable and battle
tested. You can dig through their macros or look in a configure script to
see how they generate abs_builddir, abs_srcdir, abs_top_builddir, ...
- Daniel
On Fri, 9 Oct 2020, Cristian Morales Vega wrote:
I would like to
On 10/9/20 10:46 AM, Cristian Morales Vega wrote:
> I would like to send some patches making pkg-config files relocatable.
> pkg-config offers the "pcfiledir" variable to do this.
> The thing is that I need to be able to obtain prefix, libdir,
> includedir, etc. relative to the directory where the
The use of automake per se has no dependency to coreutils, does it?
No.
There is any way to obtain the path of one directory relative to
another in automake without adding a new dependency? "realpath"
implemented as a m4 macro, maybe?
Sorry, I'm clueless. Anyone else out there wi
I would like to send some patches making pkg-config files relocatable.
pkg-config offers the "pcfiledir" variable to do this.
The thing is that I need to be able to obtain prefix, libdir,
includedir, etc. relative to the directory where the .pc file gets
installed. I can easily do this with realpat
