James

This fixes the ``conan create`` command: ```diff diff --git a/conan/recipe/conanfile.py b/conan/recipe/conanfile.py index 6b8451c..1dfd944 100644 --- a/conan/recipe/conanfile.py +++ b/conan/recipe/conanfile.py @@ -1,7 +1,7 @@ import os from conan.tools.cmake import CMake, CMakeToolchain, CMakeDeps...

No, for dependencies, only linking with the targets is necessary, and only the direct dependencies declared, the transitive ones should be automatic. Definitely not the include dirs. So something like:...

But that still have the ```cmake target_link_libraries(${PROJECT_NAME} PRIVATE ${SQLite3_LIBRARIES}) ``` You are linking with the bare libraries, not the target names. The target names should be displayed when cmake runs....

I am checking in conan-center there are tons of components with ``-``, ``+``, and a mixture of lowercase and uppercase. Probably too much to require at this stage, and we...

Lets rely on the generators, if anything we want to restrict gradually in 2.X the components names, for simplicity.

Hi @derived-coder With revisions, the concept of this recipe was downloaded from this server is not that critical anymore, because as long as the revision is the same, different binaries...

> We have in our artifactory an access pattern established. Multiple conan repos with different access possibilities. Imagine a public one for foss recipes and a private one for in...

> As far as I understand your answer is now, you should only use one conan repo per artifactory instance? No, I am not saying that. You can have as...

Hi @cassava You can use ``conan remote disable *`` to disable remotes. In any case please note: - ``conan info`` will only hit the cache if the packages are already...

Hi @ohunter Conan can make it trivial to cross-compile something, depending of course on the capabilities of the underlying build system, and also the quality of the build scripts of...