-
-
Notifications
You must be signed in to change notification settings - Fork 113
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
Fix output directory for copied byproducts #568
Conversation
I'm curious what the background of this PR is. Did you experience an issue with a multi-config generator? |
Yes, I am having an issue where an executable is being copied to my |
ae9aa5b
to
89a6f2d
Compare
Apologies for the lockfile changes, don't know what is up with them. Want me to revert them? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the long delay in reviewing this.
I am having an issue where an executable is being copied to my build directory, not my build/Debug (or whatever) directory. This is with the VS generator. Some tests are failing, so I need to see if that is due to it assuming the behavior I was seeing, or if the behavior I was seeing is due to something complex I haven't found yet.
What kind of tests are failing? Corrosions tests or tests from your project?
I guess changing the default location the artifact is copied to in Multi-Config mode has the potential to break user code, so we would need to document it in the release notes and also give a short reason what this change fixes.
Apologies for the lockfile changes, don't know what is up with them. Want me to revert them?
That would be nice.
The output directory tests were failing, but after a couple rounds of revision I managed to fix that. |
Failing test is not due to me I think |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at this again, I noticed that we unconditionally append the config_type now, when the expected behavior is to only append the config_type if the OUTPUT_DIRECTORY variable is not a generator expression
7e81465
to
a3c3975
Compare
Thanks! And sorry for the long review times |
Hey, if you can put up with long times between me responding to review, I can put up with long review times, thanks! |
CMake doesn't automatically append the config type to the output dir when using a custom command.