Use set_property for boost

[db4]

Specify library name and version: boost

---

• I've read the guidelines for contributing.
• I've followed the PEP8 style guides for Python code in the recipes.
• I've used the latest Conan client version.
• I've tried at least one configuration locally with the
  conan-center hook activated.

[ghost]

I detected other pull requests that are modifying boost/all recipe:

• [boost] Apply patch to fix https://github.com/boostorg/graph/issues/268 #6132
• boost: use clang-win toolset when compiler=Visual Studio and compiler.toolset=ClangCL #4749

This message is automatically generated by https://github.com/ericLemanissier/conan-center-conflicting-prs so don't hesitate to report issues/improvements there.

[conan-center-bot]

All green in build 2 (6a867337512e89e71b5ccb405e10dfd494072300):

• boost/1.70.0@:
  All packages built successfully! (All logs)

• boost/1.69.0@:
  All packages built successfully! (All logs)

• boost/1.74.0@:
  All packages built successfully! (All logs)

• boost/1.73.0@:
  All packages built successfully! (All logs)

• boost/1.71.0@:
  All packages built successfully! (All logs)

• boost/1.76.0@:
  All packages built successfully! (All logs)

• boost/1.72.0@:
  All packages built successfully! (All logs)

• boost/1.75.0@:
  All packages built successfully! (All logs)

• boost/1.77.0@:
  All packages built successfully! (All logs)

[SpaceIm]

If I understand conan-io/conan#8533 (comment), we should avoid to move to set_property() in CCI for the moment.

[db4]

If I understand conan-io/conan#8533 (comment), we should avoid to move to set_property() in CCI for the moment.

You may be right but

• there are many PRs already merged that add set_propery to CCI. e.g. openssl-3.x.x: Migrating names and build_modules to set_property format #8059 Use set_property for libcurl #8010 etc.
• conan 1.42.x makes my recipes without set_property just unusable with CMakeDeps generator. What can be done right now? I understand CMakeDeps is experimental but breaking everything by releasing the next version of Conan is too much.

[SpaceIm]

there are many PRs already merged that add set_propery to CCI. e.g. openssl-3.x.x: Migrating names and build_modules to set_property format #8059 Use set_property for libcurl #8010 etc.

It was before conan-io/conan#8533 (comment)

conan 1.42.x makes my recipes without set_property just unusable with CMakeDeps generator. What can be done right now? I understand CMakeDeps is experimental but breaking everything by releasing the next version of Conan is too much.

Yes, here is the issue: conan-io/conan#9943.

Due to conan-io/conan#9943 and unstability of set_property() (conan-io/conan#8533 (comment)), there is no way support both cmake_find_package_* and CMakeDeps generators in a reliable way.

[db4]

@SpaceIm your point is taken. So what do now: just close the PR or live it open until better times arrive?

[madebr]

I would close it.
There will be a point in the not-so-distant-future where we will have to modify all recipes to support conan 2.0.