Added a vcpkg manifest file (vcpkg.json) and VS2019 and 2022 batch files for setting up vcpkg and building all dependencies in manifest mode - this allows us to use a slightly newer May 2022 vcpkg and finally upgrade to GDAL 3.4.3.
Does not break the previous build procedure, which can still be used.
Type of change
[ ] New feature (non-breaking change which adds functionality)
How Has This Been Tested?
Built on two different local machines, both running Windows 10, one with VS2022 and the other with VS2019.
Checklist:
[ ] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[X] I have checked my code and corrected any misspellings
[ ] I have tagged the reviewers in a comment below incase my pull request is ready for a review
[ ] I have signed the commit message to agree to Developer Certificate of Origin (DCO) (to certify that you wrote or otherwise have the right to submit your contribution to the project.) by adding "--signoff" to my git commit command.
Pull Request Template
Description
Added a vcpkg manifest file (vcpkg.json) and VS2019 and 2022 batch files for setting up vcpkg and building all dependencies in manifest mode - this allows us to use a slightly newer May 2022 vcpkg and finally upgrade to GDAL 3.4.3.
Does not break the previous build procedure, which can still be used.
Type of change
How Has This Been Tested?
Built on two different local machines, both running Windows 10, one with VS2022 and the other with VS2019.
Checklist: