There seems to be a weird issue with toolset and host OS version, that
makes x86 Windows builds of capstone misbehave. It is not quite clear,
what is the exact issue, but switching to another runner image that also
uses a bit older toolset seems to help.
Signed-off-by: Anatol Belski <anbelski@linux.microsoft.com>
Moving to the usage of the upstream sources removes layers of
complexity present in VCPKG and allows for more flexibility with regard
to the dependency handling. Things done:
- Switch to building capstone based from an upstream tag
- Explicitly remove any unused arch support in the build
- Use static lib to simplify on-prem usage
- Cache the capstone artifacts in the pipeline
- Automatically reset cache based on the values in Makefile and
VC++ toolset version
The current capstone version is still kept 5.0-rc2. While evaluating a
possible downgrade to 4.0.2 as used by the Linux CI, some test
regressions are observed on the x64 side. If needed, those might be
spent a closer look, otherwise keeping the version seems ok.
Signed-off-by: Anatol Belski <anbelski@linux.microsoft.com>
