-
Notifications
You must be signed in to change notification settings - Fork 16
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
Revert "Export YAML_CPP_DLL define on Windows (#30)" #37
Conversation
This reverts commit efe5371.
Thanks for mentioning me! Based on #31 (comment), if we merge the 2 unmerged PRs into the foxy branch, the warnings will not appear. The PRs cannot be merged into rolling because #30 is not in rolling. I am hesitant on the revert because it will reintroduce #10, causing some packages that currently build to not build. |
True, though this bug has been in Foxy for a long time and the fix has not been released yet. So, any packages that currently build against Foxy probably already had to workaround the issue, unless they are building Foxy from source. I guess we can leave the patch in Foxy, I think the only downside is that it will cause a build warning on Windows for any packages that currently have the workaround (including some of the package in our ros2.repos file). Pinging @ros2/team for thoughts. |
Just to provide more information, not all packages have this workaround, such as robot_localization. I'm sure there's also other packages without this workaround since Windows support is usually not a main concern. |
I suppose we need to determine why removing the workaround on Rolling results in failure to build. |
And further, we should probably just close this PR. This code that this is removing is what is actually making things work on Foxy :). |
Make sense to me. Here's ports of #30 to Rolling and Humble: |
This reverts commit efe5371.
The change is causing MSBuild warnings, so I'm hesitant to release this change into Foxy. If we want to consider it, we should at the very least resolve the warnings coming from core packages (see #31 (comment)).
FYI @Ace314159