wt: add version 4.10.1

[toge]

Specify library name and version: wt/4.10.1

---

• 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.

[ghost]

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

• Bump wt's zlib requirement to [>=1.2.11 <2] range #20198
• Allow to set ENABLE_HARU and WT_RASTERIMAGE_IMPLEMENTATION #18009

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

[AbrilRBS]

Any idea what the issue might be?

[uilianries]

Any idea what the issue might be?

My guess is some missing support from that compiler version. I'll check locally.

[uilianries]

Just like I suspected ... Some features of C++ has been removed in C++17 causing compilation errors.

I was able to reproduce the same error as the CI, then I tried with compiler.cppstd=14 and worked.

In that case, we will need check_max_cppstd, but there is a problem: It's not ported to Conan 1.x and will not be ... So we will need a workaround:

conan-center-index/recipes/opencv/2.x/conanfile.py

Line 413 in 7483e5b

# FIXME: check_max_cppstd is only available for Conan 2.x. Remove it after dropping support for Conan 1.x

[uilianries]

@toge I was added the workaround with check_max_cppstd. It should fix the Conan 2.x situation.

[conan-center-bot]

Conan v1 pipeline ✔️

All green in build 5 (9e41960574a939dac3bdc646a5b6dbd80a6ee548):

• wt/4.10.0:
  All packages built successfully! (All logs)

• wt/4.7.1:
  All packages built successfully! (All logs)

• wt/4.10.1:
  All packages built successfully! (All logs)

• wt/4.9.1:
  All packages built successfully! (All logs)

• wt/4.6.2:
  All packages built successfully! (All logs)

• wt/4.6.0:
  All packages built successfully! (All logs)

• wt/4.8.0:
  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 5 (9e41960574a939dac3bdc646a5b6dbd80a6ee548):

• wt/4.7.1:
  All packages built successfully! (All logs)

• wt/4.10.1:
  All packages built successfully! (All logs)

• wt/4.10.0:
  All packages built successfully! (All logs)

• wt/4.9.1:
  All packages built successfully! (All logs)

• wt/4.6.2:
  All packages built successfully! (All logs)

• wt/4.8.0:
  All packages built successfully! (All logs)

• wt/4.6.0:
  All packages built successfully! (All logs)

[uilianries]

LGTM

[SpaceIm]

Just like I suspected ... Some features of C++ has been removed in C++17 causing compilation errors.

I was able to reproduce the same error as the CI, then I tried with compiler.cppstd=14 and worked.

In that case, we will need check_max_cppstd, but there is a problem: It's not ported to Conan 1.x and will not be ... So we will need a workaround:

conan-center-index/recipes/opencv/2.x/conanfile.py

Line 413 in 7483e5b

# FIXME: check_max_cppstd is only available for Conan 2.x. Remove it after dropping support for Conan 1.x

Did you report this issue upstream? It's quite unfortunate to have this kind of regression in latest version, specially for conan users for whom default detected profile tends to set cppstd to 17.

[uilianries]

@SpaceIm no, but looking the upstream, there is a workaround using a define:

emweb/wt@7956a40

[SpaceIm]

So why is there max cppstd? Is it not supposed to work with C++17 and above? This commit is part of 4.10.1

[uilianries]

Yes, but will need a new PR reverting and passing a new define to the compiler. I'll open it.

[SpaceIm]

Thanks 😄