cpp-lazy: add version 8.0.0

[toge]

Specify library name and version: cpp-lazy/8.0.0

cpp-lazy/8.0.0 has added support for modules, fmtlib is now required regardless of whether standalone is set or not if the module is not exported.

MarcDirven/cpp-lazy@v7.0.2...v8.0.0

---

• I've read the contributing guidelines.
• I've used a recent Conan client version close to the currently deployed.
• I've tried at least one configuration locally with the conan-center hook activated.

[conan-center-bot]

Conan v1 pipeline ✔️

All green in build 2 (f7565ac168f283761ff7a1814d4c507d8e84173d):

• cpp-lazy/6.0.0:
  All packages built successfully! (All logs)

• cpp-lazy/8.0.0:
  All packages built successfully! (All logs)

• cpp-lazy/7.0.2:
  All packages built successfully! (All logs)

---

Conan v2 pipeline ✔️

Note: Conan v2 builds are now mandatory. Please read our discussion about it.

All green in build 2 (f7565ac168f283761ff7a1814d4c507d8e84173d):

• cpp-lazy/8.0.0:
  All packages built successfully! (All logs)

• cpp-lazy/7.0.2:
  All packages built successfully! (All logs)

• cpp-lazy/6.0.0:
  All packages built successfully! (All logs)

[jwillikers]

Shouldn't this be a proper requirement in the conanfile.py then?

[RubenRBS]

Looks like so to me too @toge :)

[toge]

@jwillikers @RubenRBS
Sorry for the late reply.
If the user has defined LZ_STANDALONE and LZ_MODULE_EXPORT, cpp-lazy does not require the fmtlib.
Once LZ_MODULE_EXPORT is defined, cpp-lazy will require the C++ module.
Since cpp-lazy supports c++11 or later, it is not a portable test.
If we want to keep the portability of cpp-lazy, I think we would require fmtlib only in tests.