[vcpkg-tool-swig] Add new tool port

[cbentejac]

• [x] Changes comply with the maintainer guide.
• [x] 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.
• [x] 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.
• [x] The versioning scheme in vcpkg.json matches what upstream says.
• [x] The license declaration in vcpkg.json matches what upstream says.
• [x] The installed as the "copyright" file matches what upstream says.
• [x] The source code of the component installed comes from an authoritative source.
• [x] The generated "usage text" is accurate. See adding-usage for context.
• [x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• [x] Only one version is in the new port's versions file.
• [x] Only one version is added to each modified port's versions file.

[cbentejac]

@microsoft-github-policy-service agree

[JonLiu1993]

@cbentejac, Thanks for your PR, looks the PR build failed in many triplets, this is error log, please take a look:

CMake Error at ports/swig/portfile.cmake:26 (file):
  file COPY cannot find "/mnt/vcpkg-ci/p/swig_x64-linux/bin/Lib": No such
  file or directory.
Call Stack (most recent call first):
  scripts/ports.cmake:170 (include)

[m-kuhn]

It's a tool, should this be a release only build?

F.t.r. there's an alternative (similar): ports/swig/portfile.cmake

[JonLiu1993]

Ping @cbentejac for response.

[cbentejac]

Thanks @dg0yt for your feedback. I renamed the port and applied your suggested changes. I haven't added a test project yet, though.

[JonLiu1993]

Pinging @cbentejac Can you address the review suggestions? Thanks!

[JonLiu1993]

Note: I will be converting your PR to draft status. When you respond, please revert to "ready for review". That way, I can be aware that you've responded since you can't modify the tags.

[m-kuhn]

@cbentejac do you have plans to continue working on this in the near future?

[cbentejac]

Hi @m-kuhn,

Yes, I'm planning on finishing this port but haven't been able to find the time to wrap it up lately.