conan-clion-plugin icon indicating copy to clipboard operation
conan-clion-plugin copied to clipboard

Conan in CLion Remote Development

Open martin-zaenker-pix4d opened this issue 3 years ago • 4 comments

Hi there,

I have a conan based project and tried to work on it via CLions remote development. So far I did not see an obvious way how this works together with the conan plugin: I can see only how it works locally. Is there a way to work around that with the current plugin? Do you have a any plans to make the plugin working with CLions remote development?

martin-zaenker-pix4d avatar Aug 03 '20 16:08 martin-zaenker-pix4d

Personally I would also love a more integrated support for remote development. But nothing prevents you from using the terminal and doing all the steps by yourself (so it is not a show stopper).

  1. ssh to remote machine
  2. perform conan install there
  3. refresh cmake on the ide
  4. profit

Hopobcn avatar Oct 11 '20 15:10 Hopobcn

It is not a blocker, but would smoothen the workflow with conan + clion. Currently there is too many tasks that require the terminal, so for me using the plugin provides more overhead (keeping track of what works, and what does not), than it helps. Is there any efforts planned in the midterm to improve this combination? I am happy to come back to this plug-in once it has matured. Until than its the terminal.

martin-zaenker-pix4d avatar Oct 12 '20 11:10 martin-zaenker-pix4d

Personally I would also love a more integrated support for remote development. But nothing prevents you from using the terminal and doing all the steps by yourself (so it is not a show stopper).

1. ssh to remote machine

2. perform conan install there

3. refresh cmake on the ide

4. profit

@Hopobcn I tried doing just this, but it seems that the CMAKE_BINARY_DIR changes to the project directory, instead of the build directory, when building for remote. Thus, include(${CMAKE_BINARY_DIR}/conanbuildinfo.cmake) in CMakeLists.txt causes step 3 to fail since it looks in the project directory, not the build directory, for conanbuildinfo.cmake. Did you face this issue, and if so, how might I solve it? Sorry if it's very basic; I'm completely new to Conan (used to use Vcpkg).

SwiftWinds avatar Nov 07 '20 03:11 SwiftWinds

It would be great to see this fixed. I use Fedora Silverblue and run my workflows in containers, but I have Conan installed in the containers and not installed locally.

jwillikers avatar Jun 18 '21 18:06 jwillikers