Figure out how sdists are going to work

[shiftinv]

Ideally, we will have prebuilt wheels available for any platform. Still, there needs to be an sdist for local building, just in case.

The main issue with this is vcpkg. As always.
We can't exactly bundle a 170MB full git checkout in the sdist, but we sort of would need to, since vcpkg requires its full git history just because of how it handles versioning ports.

Really the only approach I can think of, is checking for and potentially unshallowing the submodule in CMakeLists prior to building, see here for instance. It does seem a bit hacky though? shrug

[shiftinv]

The one very hands-off alternative I can imagine is just requiring users to have a vcpkg binary in their $PATH, but it would have to be a recent enough checkout and would also just be plain annoying in terms of UX.

[shiftinv]

https://scikit-build-core.readthedocs.io/en/latest/configuration/index.html#configuring-source-file-inclusion could be relevant here, it's roughly what I meant by unshallowing the submodule in CMakeLists in the initial post

[onerandomusername]

Prepare_env.sh? Or something somewhat like that, where it can checkout the repository and put it at a specific location with a specific git hash?

[shiftinv]

Sort of, yea. Though it should be cross-platform, so either in cmake or python.