[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #57914] abspath does resolve symlink
From: |
Steffen Dettmer |
Subject: |
[bug #57914] abspath does resolve symlink |
Date: |
Tue, 31 Mar 2020 14:07:59 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36 |
Follow-up Comment #3, bug #57914 (project make):
Hi,
thanks so much for your quick reply and detailed explanation!
For my understanding I added:
/tmp/57914/subdir -> .
and found correctly:
make -f subdir/Makefile
$(abspath subdir/Makefile) == /tmp/57914/subdir/Makefile
as well as my (non-)issue:
make -C subdir
make: Entering directory '/tmp/57914'
$(abspath Makefile) == /tmp/57914/Makefile
make: Leaving directory '/tmp/57914'
Did I understand correctly:
With saying after chdir its "physical" this means this is how the
OS/kernel/POSIX(?) sees it and thus make sees it, too?
So my shell has special features to "emulate" that it looks as if it would be
"logical"?
This confused me, because in cmake its exactly the other way around: it is not
possible (without recompilation of cmake) to use physical paths; they are
(almost) always logical. I now understand that cmake tries to mimic the shells
behavior (with more or less success). Probably this is required since cmake
does not support relative paths (like autoconf/automake do) but has everything
absolute, and to avoid breaking $HOME symlinking to "randomized" mountpoints.
What a pitty.
Could you please tell me if I understood correctly of, if possible, point me
to a place where I can read more, please?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57914>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [bug #57914] abspath does resolve symlink,
Steffen Dettmer <=