Drop the complex and undermaintained build system vendored into the
port.
Use msbuild for windows, and autotools otherwise.
Note: Users who change options via triplet files
(`VCPKG_CMAKE_CONFIGURE_OPTIONS`) must/can migrate to the official
options (via `VCPKG_CONFIGURE_MAKE_OPTIONS`; no equivalent for
msbuild?).
Should resolve#32888 according to my earlier ["the build also succeeds
with the official autoconf build
system."](https://github.com/microsoft/vcpkg/issues/32888#issuecomment-1662730210)
Should resolve#36777.
* !wip Use targets to organize build
* !wip Add separate file list for MSVC builds
* Restructure to match autoconf
I re-ordered everything so it is easier to compare directly with the
project's autoconf build files.
* Move config files to expected location
* Convert CONTROL file to manifest file
Use vcpkg helper ports.
* Use sqlite3's approach to creating config file
* Fix MSVC source list
I was originally using libsodium:master as a reference, not the release.
* Turn off tests
* Fix definition scope
* Fix JSON formatting
Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com>
* Update libsodium version metadata
* [libsodium] Fix x64-windows-static[-md] builds
* [libsodium] Update port version metadata
Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com>
* Glob headers and sources on Windows
* [libsodium] Fix GLOB on Windows
* [libsodium] Update verson hash
Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com>
