[lib3mf] New port. Introduces version 2.3.2

[vijaiaeroastro]

This PR introduces a new port for lib3mf. The version is 2.3.2

• Changes comply with the maintainer guide.
• The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
• Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx.
• The versioning scheme in vcpkg.json matches what upstream says.
• The license declaration in vcpkg.json matches what upstream says.
• The installed as the "copyright" file matches what upstream says.
• The source code of the component installed comes from an authoritative source.
• The generated "usage text" is accurate. See adding-usage for context.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is in the new port's versions file.
• Only one version is added to each modified port's versions file.

[vijaiaeroastro]

@microsoft-github-policy-service agree company="3MF Consortium"

[vijaiaeroastro]

@dg0yt I have made the following changes

• Removed all instances where i checked for "vcpkg" tool chain
• Removed dependency version from vcpkg.json file and lib3mfConfig.cmake files

I will discuss and implement your other suggestions in the upstream project in future releases.

[vijaiaeroastro]

@WangWeiLin-MV Could you please let me know if all the issues have been resolved? Thanks.

[vijaiaeroastro]

@WangWeiLin-MV I have committed the requested changes.

[WangWeiLin-MV]

The port usage tests pass with the following triplets:

• x64-linux
• x64-windows

Invalid check after update.

[WangWeiLin-MV]

The port usage tests pass with the following triplets:

• x64-linux
• x64-windows

[vijaiaeroastro]

@WangWeiLin-MV @dg0yt Thank you so much for valuable time and comments.

[BillyONeal]

Here these are controlled by VCPKG_TOOLCHAIN but elsewhere they're controlled by separate options. What controls find_dependency should always match what controls it in the CMakeLists.txt

[BillyONeal]

As written the patch seems inapplicable for either the goal of minimizing the size of the patch in vcpkg, as well as the goal of matching exactly what upstream should do. To that end, I would like to see something like one of the following.

Option A: Minimize the size of the patch to only what vcpkg needs to touch, I've submitted as 3MFConsortium#2

Option B: Actually wire up the new options correctly with respect to what upstream needs to do to be correct in their CMake configs; I've submitted that as 3MFConsortium#3

[vijaiaeroastro]

@BillyONeal Thank you so much for taking the time. I have accepted your Option A. Kindly check and let me know if its good enough to be approved.

[WangWeiLin-MV]

The port usage tests pass with the following triplets:

• x64-linux
• x64-windows

[BillyONeal]

Thanks for the new port!