https://bugs.kde.org/show_bug.cgi?id=412477
Bug ID: 412477
Summary: meson support not working when meson is a symlink
Product: kdevelop
Version: 5.4.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Build tools: Meson
Assignee: kdevelop-bugs-n...@kde.org
Reporter: 2...@gmx.de
Target Milestone: ---
When I try to use meson with kdevelop I always get error messages like:
/home/../project> /usr/lib64/python-exec/python-exec2 --reconfigure
/home/../project/build
/usr/lib64/python-exec/python-exec2: python-exec2 is a wrapper, it must not be
run directly.
*** Failure: Exit code 127 ***
The problem arises because kdevelop seems to resolve symlinks itself before
running the corresponding executable. But on gentoo systems python-scripts are
all symlinks to python-exec. When kdevelop resolves the symlink
/usr/bin/meson->/usr/lib64/python-exec/python-exec2 the original name is lost
and python-exec doesn't know that to do.
Solutions:
Kdevelop shouldn't resolve the symlink itself.
--
You are receiving this mail because:
You are watching all bug changes.
