Source SDK repository separated from the engine

[LegendaryGuard]

This discussion is related to #101 and can be considered as duplicated. If #101 issue is re-opened, let's delete this post and continue into #101 to find ways and solutions to solve that.

Wouldn't be great to have the SDK separated or having a separated SDK version from this main repository? Although, if it were treated as submodule, it would be splendid to use.

Also, I think getting separated the SDK, it would need documentation about how to compile with waf to avoid some people being confused with SDK 2013 build tools.

I think using the SDK in this main repository would be using with the following command (I don't remember the other targets, but I believe that the compiled ones for game logic are these):

./waf build --target=client,server

Not sure if that applies when exists a SDK repository being separated from the main repository, the build configuration may change the way of executing the parameters to use SDK repository.

[LegendaryGuard]

I've some news, I updated the forked SDK (I made a branch to distinguish the updates and check the build workflows): https://github.com/LegendaryGuard/source-sdk-2022/tree/2023-update

I checked this fork, it hadn't dx9sdk, so that caused errors when trying to build. After that, I fixed and everything is working a expected.
OTOH, not sure if this is the legal way to use Source SDK.
It would be cool to have a SDK using WAF without any concern about legal terms.