Skip to content
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

add submodules as dirs when build in vscode #202

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

milyin
Copy link
Contributor

@milyin milyin commented Sep 3, 2024

fix for #201

Copy link

github-actions bot commented Sep 3, 2024

PR missing one of the required labels: {'dependencies', 'internal', 'breaking-change', 'enhancement', 'bug', 'new feature', 'documentation'}

@@ -39,7 +39,9 @@ endfunction()
# loaded as root project into vscode
#
function(declare_cache_var_true_if_vscode var docstring)
if(CMAKE_CURRENT_BINARY_DIR STREQUAL "${CMAKE_CURRENT_SOURCE_DIR}/build")
if((CMAKE_CURRENT_BINARY_DIR STREQUAL "${CMAKE_CURRENT_SOURCE_DIR}/build") AND
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is unclear why we should favor vscode over anything else.

@DenisBiryukov91
Copy link
Contributor

Trying to install zenoh-cpp using this approch would lead to a lot of non-evident effects: i.e depending on zenoh-c/pico implementation the user-installed zenoh-c/pico libraries might be overwritten or otherwise nor zenoh-c nor zenoh-pico would be installed and thus the user will end up with a broken zenoh-cpp installation (i.e none of the zenoh-cpp dependent packages will work including zenoh-cpp standalone examples)

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

Successfully merging this pull request may close these issues.

2 participants