Open lambtonr opened 1 day ago
Hi @lambtonr
Thanks for your feedback.
I am trying to understand your setup, but I am afraid that I am missing some details.
It is not very clear how the cmake-conan
is playing together with the rest, specially because I see that you are also running conan install
too. If it is possible, I'd like to leave cmake-conan
out of the issue, and it would be better to replicate the issue with conan install
+ cmake --presets
commands instead.
For example, the final cmake --build --prefix conan-release
is difficult to understand, because if using the cmake-conan
, then the Conan presets cannot be used, because they are generated after Conan is invoked, but if using cmake-conan
, this happens inside CMake, so not possible.
Then, there are some details that are not clear for example the first: conan install .
it is not clear in which folder this is happening, in the say
package, in the image
package, in neither of those? If it is done in another place, what is the conanfile
that is at that place?
What is your question?
Hi,
I am trying to diagnose a problem with my conan recipe / project cmake. The recipe was originally a out of source recipe and working for default build but wont link to CUDA when using 'with_cuda" option.
To try and debug this i have moved the recipe to be an in source recipe, and was trying to use the conan editable tutorial from here: https://github.com/conan-io/examples2/tree/main/tutorial/developing_packages/editable_packages
However when i do cmake --build --prefix conan-release i get the following:
it seems like CMakeUserPresets.json contains the following includes:
i also end up with the duplicate generators seen here under my /build/Release/ directory:
If i remove the "build/Release/conan/build/Release/generators/CMakePresets.json" include i can run the build and it works.
In addition to the editable package issue, when i try and use the editable package i get the following:
Many Thanks
Have you read the CONTRIBUTING guide?