Rather than hardcode a bunch of SDK stuff, this is an attempt to move
SDK information to a declarative model. Each SDK gets a manifest, and
the manifests are stored in a shared repository.
Manifests encode stuff like "what platforms does this SDK build on" and
"what link flags do I need on each architecture".
This will hopefully reduce the complexity of the build scripts, since
going forward we only have to add new manifests, rather than figure out
how to attach more gunk into the build logic.
* Initial PVKII branch support
* Fix compiler error
* Add missing SE_PVKII check
* Update checkout-deps with 'pvkii'
* Change PVKII code to 10 and bump others by 1, including recommended change in provider_ep2.cpp:135
* Start using Github Actions
Test on all platforms. SourceHook tests are broken on windows
so allow failures until they're fixed.
* Only run the workflow for the master branch
* Enable Insurgency and Blade Symphony x64 builds
The HL2SDKs were updated to support compilation and linking on x64 before. #67 allowed to load MMS on Blade Symphony Win64. AMBuild 2.2 allowed to build for multiple architectures in one build script on Windows.
#76
* Add Insurgency to AppVeyor SDKs to test win64 builds
* Try to enable x64 builds on appveyor
* I don't know PowerShell syntax
* Split the envvar before usage
Thanks psychonic!
* Fix detection of Blade Symphony on Windows x64
Port finding the module base address on x64 builds from SourceMod.
Fix a bunch of truncation warnings on x64 while at it too.
* Fix mm_TrimComments stripping last char before comment
```c
char test[] = "hi this is a a test!// comment";
mm_TrimComments(test);
puts(test); // prints "hi this is a test" without the !
```
* Fix unsigned comparison warnings
* Fix truncation warnings in SourceHook::String
* Fix unsigned comparison warnings
clang does have some nice analysis.
With the current version of the script, it’s not easy for a beginner to compile a sample mm plugin.
In fact, we need to set when we configure the build the SDK and the mm path. It’s not very clear for beginners + the script crash with an exception which cause a confusion
With this version, just make build directory, do a configure in direction then, build => enjoy!
