diff options
author | Eli Schwartz <eschwartz93@gmail.com> | 2025-03-26 11:26:21 -0400 |
---|---|---|
committer | Eli Schwartz <eschwartz93@gmail.com> | 2025-03-26 16:09:37 -0400 |
commit | 19482e4553775d4612f5fcc1c7c124774e9a0f79 (patch) | |
tree | 4c1d60fb5c1fcdd3646b37ec15ee52e27e8b57fb /docs/markdown/snippets/rustdoc.md | |
parent | 8afce56719272bb5367c5ae304b3a935962a5391 (diff) | |
download | meson-19482e4553775d4612f5fcc1c7c124774e9a0f79.zip meson-19482e4553775d4612f5fcc1c7c124774e9a0f79.tar.gz meson-19482e4553775d4612f5fcc1c7c124774e9a0f79.tar.bz2 |
select the correct meson_command for pyinstaller builds, even on not-Windows
We have previously updated the python_command handling to correctly
detect PyInstaller builds without assuming that it is only Windows, back
in commit c39ee881a1959ae37aded8e0c24cec23b2bd6a90. But the fix was
incomplete. This affects e.g. running --internal scripts such as
symbolextractor.
The issue in this case is slightly more subtle. While sys.executable
won't be a valid python so it intuitively falls over quite badly when
trying to run it as one, getting the original command is broken in a
more interesting way. PyInstaller sets `sys.argv[0]` to the basename of
the executable, which then got absolutized to a nonexistent file in the
current working directory.
Fixes: https://github.com/mesonbuild/meson/issues/14412
Diffstat (limited to 'docs/markdown/snippets/rustdoc.md')
0 files changed, 0 insertions, 0 deletions