Skip to content
This repository has been archived by the owner on Jul 12, 2024. It is now read-only.

Cookbook discussion #33

Closed
traversaro opened this issue Oct 29, 2018 · 3 comments
Closed

Cookbook discussion #33

traversaro opened this issue Oct 29, 2018 · 3 comments
Assignees

Comments

@traversaro
Copy link
Contributor

traversaro commented Oct 29, 2018

Describe the bug
Not really a bug, just a couple suggestion for the Cookbook available at https://github.com/ms-iot/ROSOnWindows/blob/master/Porting/Cookbook.md . If you agree with them, I would be happy to provide a PR for modifying the Cookbook.

Visibility macros

For dealing with visibility issues, the cookbook suggests to use the CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS CMake property.

However, the fallback solution of directly declaring the visibility macros LIB_EXTERN has some drawbacks in its current form:

Threat warning an errors

The suggest settings for warnings ( https://github.com/ms-iot/ROSOnWindows/blob/master/Porting/Cookbook.md#all-warnings ) is to include the /WX flag, that will make every warning an error. This may be problematic because if a new version of Visual Studio that introduces a new warning is available, the compilation could fail. Furthermore, it is inconsistent with the corresponding GCC warnings -Wall -Wextra, that do not contain -Werror.

@ooeygui
Copy link
Member

ooeygui commented Nov 1, 2018

Hi @traversaro,
Thank you for the feedback. Please do submit a PR for updates.

Visibility
Please do a pull request to clarify this section. It's one of the more obscure issues when porting, so we'd like to minimize the pain.

Warning as Errors
I updated the documentation to clarify, as well as how to disable specific warnings.

Thank you!

@ooeygui ooeygui self-assigned this Nov 1, 2018
traversaro added a commit to traversaro/ROSOnWindows that referenced this issue Nov 3, 2018
@traversaro
Copy link
Contributor Author

Thanks for the reply @ooeygui . PR on visibility added in #37 .

@ooeygui
Copy link
Member

ooeygui commented Nov 5, 2018

With your change and mine, I think we have resolved this issue. Please reopen if you believe we need further clarification

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants