Migrating the build process of the _cmd and _champ libraries from the setup.py file to CMake

[ye11owSub]

No description provided.

[JarrettSJohnson]

Looks good, but please continue to keep create_shadertext.py around.

[JarrettSJohnson]

Thanks for your efforts. I will say for the purposes of this (and future) PRs, I would ask to leave the champ module untouched for now.

[ye11owSub]

Hi @JarrettSJohnson
Can you please tell me why I shouldn't change the champ module?
I split the champ into a separate cmake, because I wanted to use it as a first step towards using pybind11 to create Python extensions

[JarrettSJohnson]

Hi, I haven't been following this PR too much, but just wanted to mention that I think the original goal for what I thought this PR would go has gone completely further than the scope that I would have liked (and this hasn't been the first time this has happened).

I think eventually we want to get there, but it really is important to me that we keep the building process of incentive and open-source in-sync. The original refactoring of setup.py was fine, but the full cmake-ify (if I were to consider something like scikit-build-core or something) of this something I'd like to handle myself and incrementally.

[ye11owSub]

hey @JarrettSJohnson
Is there any chance that you could share your plan, so we can discuss the steps that need to be taken in this PR in order to switch to CMake?