[fast-double-parser] update to 0.8.0

[jiayuehua]

• Changes comply with the maintainer guide
• SHA512s are updated for each updated download
• The "supports" clause reflects platforms that may be fixed by this new version
• Any fixed CI baseline entries are removed from that file.
• Any patches that are no longer applied are deleted from the port's directory.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is added to each modified port's versions file.

[Osyotr]

The library now installs cmake config, so the port should use vcpkg_cmake_* functions instead of just copying a header file.

[BillyONeal]

This is still commented out, it seems this is still being worked on?

[jiayuehua]

this comment is not needed . I just Have deleted this comment .

[dg0yt]

IMO this should be handled with vcpkg_cmake_config_fixup(PACKAGE_NAME fast_double_parser):

fast-double-parser:x64-linux:/share/fast_double_parser/fast_double_parser-config.cmake
fast-double-parser:x64-linux:/share/fast_double_parser/fast_double_parser-targets.cmake

[Cheney-W]

@jiayuehua
Could you please follow dg0yt's suggestion to add a call to the vcpkg_cmake_config_fixup function in the portfile.cmake file? At the same time, you need to add the vcpkg-cmake-config dependency in the vcpkg.json file.
Although calling this function will not change the current output files or layout of this port, doing so can help prevent potential issues in the future if the upstream modifies the exported contents.

[Osyotr]

Although calling this function will not change the current output files or layout of this port

This is because of the spurious set(VCPKG_BUILD_TYPE release) in the portfile.

[jiayuehua]

@jiayuehua

Could you please follow dg0yt's suggestion to add a call to the vcpkg_cmake_config_fixup function in the portfile.cmake file? At the same time, you need to add the vcpkg-cmake-config dependency in the vcpkg.json file.

Although calling this function will not change the current output files or layout of this port, doing so can help prevent potential issues in the future if the upstream modifies the exported contents.

ok I will follow dg0yt's advice summit the change later.

[BillyONeal]

Although calling this function will not change the current output files or layout of this port

This is because of the spurious set(VCPKG_BUILD_TYPE release) in the portfile.

How is it "spurious"? Is the library not header only any longer?

[Osyotr]

How is it "spurious"? Is the library not header only any longer?

I was thinking about interface properties in debug config, but now I see that set(VCPKG_BUILD_TYPE release) + vcpkg_cmake_config_fixup is widely used in vcpkg.
https://github.com/search?q=repo%3Amicrosoft%2Fvcpkg+set%28VCPKG_BUILD_TYPE+vcpkg_cmake_config_fixup&type=code

[BillyONeal]

Thanks for the update!