You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lately I've been trying to package https://github.com/nanopb/nanopb. The problem is that it requires that the "protobuf" python library be installed. Is this something that conan can reasonably handle without resorting to system_requirements? If I have to go the system_requirements route is there any support for controlling the behaviour using say python virtual environments? Ideally I was thinking that I could add the library as a system_requirements, and activate a python virtualenv in which I could install the requirements but conan does not provide any suppotr of changing the system_requirements environment at this moment. Is there any good way forward or should I just bite the bullet and go with system_requirements and instead sandbox the whole conan environment ?
The text was updated successfully, but these errors were encountered:
@uilianries The decisions and explanations of the Conan team are currently shattered all over the place. Could this please be documented more officially?
Lately I've been trying to package https://github.com/nanopb/nanopb. The problem is that it requires that the "protobuf" python library be installed. Is this something that conan can reasonably handle without resorting to system_requirements? If I have to go the system_requirements route is there any support for controlling the behaviour using say python virtual environments? Ideally I was thinking that I could add the library as a system_requirements, and activate a python virtualenv in which I could install the requirements but conan does not provide any suppotr of changing the system_requirements environment at this moment. Is there any good way forward or should I just bite the bullet and go with system_requirements and instead sandbox the whole conan environment ?
The text was updated successfully, but these errors were encountered: