James
James
> conan install ... conan build ... The first ``conan install`` is unnecessary and redundant, the ``conan build`` already does a ``conan install`` internally. > doesn't seem to care whether...
> We would like to keep the build and test steps separate. Also, there are some configurations where we don't need to create the package, e.g., when we run code...
> Is there any issue we should be aware of when following this approach? I know you had mentioned previously that only the public headers are available, but maybe I'm...
It is not intended to break them, it is just that at this first iteration it is not implementing MODULE, and focusing on a correct behavior for Config.cmake files, which...
Hi @anders-zpt Thanks for your question. Have you checked the full working demo at https://github.com/conan-io/conan-extensions/tree/main/demos/build-info? You can upload different build-infos, and then aggregate all of them into a single Release...
Hi @marvin-the-mathematician The PR https://github.com/conan-io/conan-center-index/pull/24288 was merged hours ago, so the new ``b2/5.2.0`` version should already be in ConanCenter. Can you please try updating your dependencies? In your case, if...
You might be able to overwrite it adding to your profile: ``` ... [tool_requires] b2/5.2.0 ``` And then passing that profile to your ``conan`` command. I guess the recipe for...
Yes, the difference is that ``` --requires=boost/1.85.0 ` --tool-requires=b2/5.2.0 ` ``` Installs the tool-requires for yourself but not for boost, while the profile ``[tool_requires]`` inject the tool-requires in all packages,...
I think this might be good feedback for @grafikrobot. At the moment I don't see any PR updating the boost recipe ``tool_require`` to latest ``b2``. As it is a major...
> Hence.. Yes, it's likely possible you can update current and previous Boost releases to use the current B2. But I can't fully guarantee it will work identically. :-) Thanks...