Open mpusz opened 6 years ago
@mpusz, thanks for reporting this issue.
I have questions:
First request after publishing the blog post in Jetbrains: https://blog.jetbrains.com/clion/2019/05/getting-started-with-the-conan-clion-plugin/#comment-96977
Any status on this?
I was able to resolve this by following this comment from conan (which automatically ran it all during the wsl build on clion): https://docs.conan.io/en/latest/howtos/cmake_launch.html
Resulting cmake snippet:
set(CMAKE_CXX_STANDARD 17)
# Download automatically, you can also just copy the conan.cmake file
if(NOT EXISTS "${CMAKE_BINARY_DIR}/conan.cmake")
message(STATUS "Downloading conan.cmake from https://github.com/conan-io/cmake-conan")
file(DOWNLOAD "https://raw.githubusercontent.com/conan-io/cmake-conan/master/conan.cmake"
"${CMAKE_BINARY_DIR}/conan.cmake")
endif()
include(${CMAKE_BINARY_DIR}/conan.cmake)
conan_cmake_run(REQUIRES Catch2/2.6.0@catchorg/stable BASIC_SETUP CONANFILE conanfile.txt BUILD missing)
include(${CMAKE_BINARY_DIR}/conanbuildinfo.cmake)
conan_basic_setup()
The same question. Any status here? The clion is installed on windows,and conan is installed in ubuntu.
I try modifying the conan launch path to
ubuntu2004.exe run ‘~/.local/bin/conan’
This works in powershell (concat conan‘s parameters ) but it doesn’t work in clion.
(sorry for my poor English)
Yes, the status is "on hold". We are working very hard to get Conan 2.0 out (already in alpha), and at the moment we don't have enough time to put on the IDE plugins, sorry. We will resume work after 2.0 GA.
That's fine, I can install the dependencies manually and hope to use Conan 2.0! :smile:
Hi, any update on this? I am testing conan 2
.
I am also using windows-based CLion with WSL linux cpp project
Edit:
I found out that the plugin uses cmake-conan
(thanks to this )
And I finally found my mistake:
the plugin needs conan
path like it's inside WSL
, e.g /usr/local/bin/conan
without $wsl
stuff,
since it runs during the cmake phase which is already inside WSL
Hi all,
Conan 2.0 got a new plugin version for CLion that is based on the new develop2
version of cmake-conan
. Both are experimental, but looking really good and promising.
Effectively, using WSL for Conan is like running in a regular Linux machine. The Conan running should be the one inside WSL. I guess that you read the instructions at the README.
So if this is working fine, maybe we can close the issue? Things are working good both from CLion and cmake-conan integrations for this use case? Thanks for the feedback!
It works for me.
Maybe it's just me, but I think there should be a note in the README regarding WSL
: that the path should be inside WSL
itself.
When I build projects on Windows using i.e. gcc on WSL, I am not able to match CMake and Conan profiles as the configuration from WSL is not read by the plugin and there is no way to provide a configuration name by hand.