Our most recent update saw some changes to tier0 that broke binary compatibility causing MM/SM to fail to load on Linux. This PR splits PVKII into its own engine branch for Metamod, and I have done a corresponding PR for SourceMod as well: https://github.com/alliedmodders/sourcemod/pull/1847
As explained there, this will also require a new hl2sdk branch for 'pvkii' which I have done here: https://github.com/Octoshark/hl2sdk-pvkii/tree/pvkii ~Again I don't see a way to do a PR that will create a new branch on the original repo. The pvkii branch is based off of sdk2013~ Looks like we've got that sorted.
As a side note that I also explained in the other PR, since we've talked about this on Discord, I did go ahead and backport the threadtools changes in that hl2sdk branch from C++20 to C++14. This should avoid any compiler headaches here.
CI will fail until the hl2sdk changes are merged in.
Our most recent update saw some changes to tier0 that broke binary compatibility causing MM/SM to fail to load on Linux. This PR splits PVKII into its own engine branch for Metamod, and I have done a corresponding PR for SourceMod as well: https://github.com/alliedmodders/sourcemod/pull/1847
As explained there, this will also require a new hl2sdk branch for 'pvkii' which I have done here: https://github.com/Octoshark/hl2sdk-pvkii/tree/pvkii ~Again I don't see a way to do a PR that will create a new branch on the original repo. The
pvkiibranch is based off ofsdk2013~ Looks like we've got that sorted.As a side note that I also explained in the other PR, since we've talked about this on Discord, I did go ahead and backport the threadtools changes in that hl2sdk branch from C++20 to C++14. This should avoid any compiler headaches here.
CI will fail until the hl2sdk changes are merged in.