Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[conan-center] Avoid collect_libs usage #424

Open
uilianries opened this issue May 31, 2022 · 1 comment
Open

[conan-center] Avoid collect_libs usage #424

uilianries opened this issue May 31, 2022 · 1 comment

Comments

@uilianries
Copy link
Member

The collect_libs is tentative as it makes our recipes much easier, however, it comes with a salt price.

  • For users, is not clear the exported libraries names, need to check the package folder or build output
  • For maintainers is not clear which library is exported according the profile (Release, Debug, shared ...)
  • When having inter dependency, it may fail because that method uses alphabetic order to sort the libraries list
@SpaceIm
Copy link
Contributor

SpaceIm commented Jan 15, 2023

Currently it's impossible to ban collect_libs(), it can be very hard to predict lib name based on:

  • the logic in upstream build files
  • informations available in user profile

Was there a discussion in conan team about issue we encounter in conan-center?
For example, see conan-io/conan#12336 (comment) for the reason why it's almost impossible currently to predict lib name for windows clang flavors when upstream CMakeLists create lib names based on MSVC variable. It leads to endless PR trying to fix a flavor and breaking another (or even MinGW gcc).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants