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.

[feature] Allow different cpp_info.name depending on the generator

See original GitHub issue

Something similar to self.cpp_info.name['my_generator'] should work. Make it compatible with cpp_info.name = 'name' syntax

Related to #5984

Issue Analytics

State:
Created 4 years ago
Reactions:2
Comments:5 (5 by maintainers)

Top GitHub Comments

2reactions

lasotecommented, Nov 19, 2019

To simplify the implementation we propose to keep the name and introduce names as the dict for the generators. Otherwise, getting the str from the cppinfo.name it is very problematic and requires ugly code. The names is much more pragmatic.

0reactions

memshardedcommented, Nov 19, 2019

@ledocc Managing internal details within a package would be part of the components feature. There was a PR open for this, but it was a bit risky and was put on hold at the moment. We would eventually resume work on the components feature, but not a priority at the moment.

Top Results From Across the Web

Attributes — conan 1.53.0 documentation

Using components and global cpp_info non-default values or release/debug configurations at the same time is not allowed (except for self.cpp_info.names ).

conan/CHANGELOG and conan Releases (Page 3) | LibHunt

Bugfix: Fix pkg_config generator adding to .pc files empty include and lib ... Docs:; Feature: Allow conan.conf user configuration of paths to client ......

cpp.texi - Apple Open Source

This feature allows you to break long lines for cosmetic purposes without changing their meaning. @item Predefined macro names are replaced with their ......

conan Changelog - pyup.io

Feature : Do not allow doing conan create/export with uncommitted changes ... of packages that are equivalent with different names for different distros....

Error installing Pystan in python 3.10 with gcc 9.2.0

Compiling pystan/_chains.pyx because it depends on /home/user/py310/lib/python3.10/site-packages/Cython/Includes/libcpp/vector.pxd.