[boost] update to 1.75.0

[yurybura]

Update Boost library to version 1.75.0
Release Notes: https://www.boost.org/users/history/version_1_75_0.html

Adds new libraries/ports: Boost.Json, Boost.Leaf, Boost.Pfr
Removes obsolete library/port Boost.Signals

Fixes #15070

[cenit]

Duplicate of #15071 ?

[yurybura]

@cenit Yes. I would like to speed up update.

[PhoebeHui]

@yurybura, thanks for your contribution!

Here is CI testing results:
telnetpp with x86-windows/x64-windows/arm64-windows/arm-uwp

D:\installed\x64-windows\include\boost/move/detail/type_traits.hpp(968): error C2079: 'boost::move_detail::alignment_of_hack<T>::t1' uses undefined struct 

symengine with arm64-windows/arm-uwp

D:\installed\arm-uwp\include\boost/multiprecision/cpp_int/intel_intrinsics.hpp(103,11): error C3861: '_addcarry_u32': identifier not found
D:\installed\arm-uwp\include\boost/multiprecision/cpp_int/intel_intrinsics.hpp(108,11): error C3861: '_subborrow_u32': identifier not found

failure logs for arm64-windows.zip

[KazDragon]

As I mentioned in the linked topic, I installed Boost 1.75 on my local machine and Telnet++ compiled and linked just fine with my mainline. So I'm not sure what's causing the problem. Any assistance would be graciously and gratefully received.

[yurybura]

@KazDragon Thank you. I'll check this issue when I can.

[longnguyen2004]

@yurybura Seems interesting, I'll certainly test this for mingw!

[yurybura]

Dear @PhoebeHui,
Could you check CI?

[longnguyen2004]

x64-osx is having problems like usual, just ignore it for now.

[PhoebeHui]

@yurybura, I have rerun the CI testing with x64-osx. It's in progress.

[cenit]

recently I experience this behaviour under linux/osx:

-- Building release...
-- Configuring x64-linux-dbg
-- Configuring x64-linux-rel
-- Building x64-linux-dbg
-- Building x64-linux-rel
-- Building debug...
-- Configuring x64-linux-dbg
-- Configuring x64-linux-rel
-- Building x64-linux-dbg
-- Building x64-linux-rel

as you can see both configs are built twice. Is it solved by this PR? I assume there might be a double loop somewhere

Note: this happens only in boost-* libs

Note2: it was decided a long time ago to build debug first, to quicken the failure in case of errors. Maybe also an inversion in the configs is required, after the double build is solved

[longnguyen2004]

@cenit That behavior has been there for a long time, and it's due to how the build helper works.
MSVC targets are handled with a CMake script, while Unixy targets are relegated to a separate CMakeLists.txt (see this and this). As a result, Unixy targets will use vcpkg_configure_cmake, which by default builds both the debug and release targets of the CMake project, which is redundant since both are essentially the same.
@ras0219-msft Is it possible to unite the two into one script, or maybe split it into multiple scripts and use include for each platform?

[cenit]

before https://github.com/microsoft/vcpkg/blob/master/ports/boost-modular-build-helper/boost-modular-build.cmake#L141 and https://github.com/microsoft/vcpkg/blob/master/ports/boost-modular-build-helper/boost-modular-build.cmake#L145 maybe we can set temporarily the VCPKG_BUILD_TYPE if not defined, so that it is not replicated internally?

[yurybura]

@PhoebeHui CI now looks good. Thank you.

[PhoebeHui]

LGTM, Thanks @yurybura!

I have tested boost-regex[icu]:x64-windows locally, it passed.

@cenit, we will fix the issue that you mentioned in another PRs.

@ras0219, could you help further review?

[cenit]

@cenit, we will fix the issue that you mentioned in another PRs.

it's just that each update is going to waste double the time in each and every CI machine using vcpkg and boost...

[BillyONeal]

Oh wait that's the before so presumably the //s are in what you're replacing.

Thanks for your contribution and yay for updated Boost!

[pdimov]

The Boost JSON library is compiled, but this adds a header-only portfile for it, so using it doesn't link. I suppose the script that generates the portfiles needs to be patched somehow, but I don't know how.

[pdimov]

The problem is that the script checks for build/Jamfile.v2:

vcpkg/scripts/boost/generate-ports.ps1

Line 398 in 5a10163

if ((Test-Path $unpacked/build/Jamfile.v2) -and $library -ne "metaparse" -and $library -ne "graph_parallel")

but libs/json/build contains a Jamfile, without the .v2. (The .v2 suffix dates from the time there was a v1 and is not required today.)