James
James
Update: The 1st approach has a challenge: to load the ``test_package/conanfile.py`` it is necessary to know the ``ref`` of the package. This is known at ``conan create`` time because it...
I have submitted a potential solution: make explicit the locking of test_package. Basically the line: ```python c.run("lock create test_package --lockfile=conan.lock --lockfile-out=conan.lock") ``` Note this is done after capturing the main...
The workaround explicitly locking ``test_package`` seems to be good atm. We probably want to revisit this after https://github.com/conan-io/conan/pull/12046, moving this to beta.4
The problem with ``check_min_cppstd(self, 11)`` is that we never clearly defined its semantics (as with most of the ``ConanInvalidConfiguration``) if it is a package that cannot exist (cannot be built)...
this will be finally closed by https://github.com/conan-io/conan/pull/12555
Closed by https://github.com/conan-io/conan/pull/12555, will be in beta.6
This PR seems related too: https://github.com/conan-io/conan/pull/11556
Hi @gabyx This was assigned for 1.51, but we didn't get any response, so I am moving it to next iteration 1.52. Please check the above comments and let us...
Hi @gabyx This PR has been stale for a few months now, we have been moving it from release to release, I hope it is not an issue anymore, so...
> conan could easily set the correct compilers Because it is not that easy. The previous integration, the ``cmake`` generator had some compiler checks. We had to provide a escape...