You can generate the Cmake files from the repository and create your own builds with the repository by using Git commands tobranch. There there is one called “lite” that shows how to do a stripped down version. This has code that shows what a minimum version looks like - which works for Cmake generation on Linux. But for windows using Cmake, you’d disable these features by ticking them off.
But basically to save you time on Windows - disable the following in your Cmake generation and build something light (instead of like 20 min, go down to 3-5 min):
- … And other things that won’t break the UI for testing purposes.
For testing branches and creating new ones, you’d need to use something like TortoiseSVN or a git like console commands to create and use the branches from their repositories. Here I wouldn’t have a clue, as in Blender I don’t know, personally I use a fork from Github, so Tortoise gives me Windows GUI systems to do branching and merging and there is a lot of info about how to use Git to sync a repository, fork it, and branch it easily (even in the Web UI) - but hopefully someone here can answer for the Bblender branches repository (from Graphicall I guess?).
But if you use Tortoise to sync to the repository, syncing from origin may give you all the branches to choose from, and the software remembers and pulls the correct branch data, and that is handy for switching back and forth. Git console commands can also do this. The repository updates to said branch, and vice versa, or merges, or whatever you want. Since the library is remote, nothing messes up unless you commit bad code.