Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[question] Fair Play

See original GitHub issue

It’d be nice to explicitly state in contribution guidelines such rules that would allow Conan repository to not be against the world, but play nicely with it.

After the Components feature comes in, each contribution should specify names in the cppinfo in accordance with the upstream project’s build scripts. Would allow users of these libraries in the native build system to plug&play Conan.
Extending https://github.com/conan-io/conan-center-index/issues/21, we should check if there same packages in the Vcpkg, another fairly popular dependency manager, and name our projects the same if so (though I understand that there could be moments when we can’t).

Issue Analytics

State:
Created 4 years ago
Reactions:3
Comments:8 (8 by maintainers)

Top GitHub Comments

3reactions

gocarloscommented, Sep 17, 2019

@danimtb after https://github.com/conan-io/conan/pull/5598 one could start using the target names for the cmake test packages as already done for zlib (https://github.com/conan-io/conan-center-index/blob/master/recipes/zlib/1.2.11/test_package/CMakeLists.txt) test package instead of using ${CONAN_LIBS}

2reactions

danimtbcommented, Sep 17, 2019

@gocarlos the issue should be mitigated by this PR in Conan https://github.com/conan-io/conan/pull/5598 where you can actually declare the “cmake name” of a library inside its recipe.

Of course, I understand naming is important and now with this repository, we can transparently discuss and fix this kind of stuff 😄