-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
extract_all_objects() with custom target results in invalid paths for subproject with Visual Studio backend #8020
Labels
Comments
I have a similar issue: |
This also happens with targets generated by |
arch1t3cht
pushed a commit
to arch1t3cht/meson
that referenced
this issue
Nov 25, 2023
The referenced issue involved the VS backend breaking when custom_targets where linked, extracted using extract_all_objects, and then linked into other targets, while in a subproject.
arch1t3cht
pushed a commit
to arch1t3cht/meson
that referenced
this issue
Aug 27, 2024
The referenced issue involved the VS backend breaking when custom_targets where linked, extracted using extract_all_objects, and then linked into other targets, while in a subproject.
arch1t3cht
pushed a commit
to arch1t3cht/meson
that referenced
this issue
Dec 20, 2024
The referenced issue involved the VS backend breaking when custom_targets where linked, extracted using extract_all_objects, and then linked into other targets, while in a subproject.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I have a build script where the input to one target is the output of
extract_all_objects()
, with some of the original object files being the output of a custom target (generator):When generating a Visual Studio solution with this project as a subproject on Windows, the paths to the object files generated by the generator are incorrect:
To Reproduce
A minimal working example can be found here.
Generate the solution using
and inspect
build/subprojects/my_subproject/[HASH]@@[email protected]
.nasm
must be available.Expected behavior
The paths should look like
system parameters
The text was updated successfully, but these errors were encountered: