[infoware] Add port of infoware library

[ThePhD]

This pull request adds a port for the C++ infoware library.

All triplets should be supported, with both dynamic and static builds available.

I could not find additional examples of CI that needed to change or more. The version of infoware being targeted by vcpkg should be 0.5.3.

[msftclas]

All CLA requirements met.

[PhoebeHui]

Could you also update the hash value?

The CI test failures:
File does not have expected hash:

      File path: [ C:/agent/_work/1/s/downloads/temp/ThePhD-infoware-v0.5.3.tar.gz ]
  Expected hash: [ 64a4f0b1027a20bf9c90bf99d638947cb1c0d6bad1b22c8b0403713c5e2c69756435906996b154989f9eaa41e5d55743d7bf5ef51f7bbf8d99eae94d29af1b2c ]
    Actual hash: [ 217bb9332214d823445e19f2c465199536e89a36faccea8cb72f8dd41a177e1739969d131ad25d1878e688a3a6cc1290c2125ef9d2205ad4fd334b24b27d491a ]

The file may have been corrupted in transit. This can be caused by
proxies. If you use a proxy, please set the HTTPS_PROXY and HTTP_PROXY
environment variables to
"https://user:password@your-proxy-ip-address:port/".

[ThePhD]

Files changes (133)

I, uh. Seem to have irreversibly ruined my git commit. One moment. ;;

[PhoebeHui]

@ThePhD, the CI test with following triplet, does it expect? could you please take a look?

infoware:x64-uwp
infoware:arm-uwp
infoware:arm64-windows

[ThePhD]

I was not expecting this: there seems to be a specific problem with MSBuild on these platforms and building the tool to generate PCI data? Works fine with Ninja; I'll try to fix it up for MSBuild. Sorry about the failed tests...!

[ThePhD]

I actually don't understand what's going on in vcpkg in these cases. I can build for the platforms listed as failures independently outside of vcpkg, invoking the CMake build and install with either Ninja or MSBuild just fine. But inside of vcpkg, I get errors like these:

Desktop/vcpkg/buildtrees/infoware/arm64-windows-dbg/pciids/pci.ids > infoware_generated/pci_data.hpp"
FAILED: infoware_generated/pci_data.hpp
cmd.exe /C "cd /D Desktop\vcpkg\buildtrees\infoware\arm64-windows-dbg && Desktop\vcpkg\downloads\tools\cmake-3.17.2-windows\cmake-3.17.2-win32-x86\bin\cmake.exe -E make_directory infoware_generated/ && Desktop\vcpkg\buildtrees\infoware\arm64-windows-dbg\infoware_pci_generator.exe Desktop/vcpkg/buildtrees/infoware/arm64-windows-dbg/pciids/pci.ids > infoware_generated/pci_data.hpp"
This version of Desktop\vcpkg\buildtrees\infoware\arm64-windows-dbg\infoware_pci_generator.exe is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher.
ninja: build stopped: subcommand failed.

I sincerely am not sure how to handle this. Maybe I should just disable the x64_uwp, arm_uwp, and arm64 builds?

[strega-nil]

@ThePhD For UWP, I have no idea what's wrong; I would just set it as fail. There's often an issue getting ports which aren't designed for it to work on UWP.

For arm64-windows, the issue that you have is that you have build tools that need to run on the host architecture, but you're always running them on the target architecture; it's completely valid to do that, but it means cross-compilation is impossible. You may want to pull a boost, and require that the host binaries are installed before building the target libraries, or you may want to just wait until we have support for tool-depends. If the latter, I would set it to fail and write a comment to the effect of This port doesn't support cross-compilation.

[ThePhD]

Is the right thing to do Supports: !(uwp|arm) or is it better to modify scripts/ci.baseline.txt?

[ThePhD]

Also, I think the x64_osx pipeline is broken...!

[PhoebeHui]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[PhoebeHui]

Currently we add the follow code when it unsupport some arch or platform.

1. CONTROL: Supports: !(uwp|arm)
2. Portfile.cmake: vcpkg_fail_port_install(ON_ARCH "arm" ON_TARGET "uwp")

@ThePhD, currently we don't need add unsupport triplet to ci baseline file, since we already have 'Support' field, could you add the warnning message for users by 'vcpkg_fail_port_install(ON_ARCH "arm" ON_TARGET "uwp")'?

[BillyONeal]

@ThePhD Thanks for your contribution!

[ThePhD]

Oh, nice, thanks for adding that function to the PR, glad it seems to all work now!!

[dan-shaw]

Thanks for the PR!