Not quite there

[OneManMonkeySquad]

First off, what a fine tool.

I tried it on our 360+ project solution. It's working but there are a few showstoppers.

• Solution settings are empty in the original .sln file and only shows up in the RB .sln file; I don't think it's supposed to be this way, maybe the .sln parser fails (I can provide you our .sln file if needed)
• Can't search (or press C to get to the first C.. project) in the solution settings; We have a lot of .cpp which have to be build alone
• An automatic fallback for .cpp files which don't work in jumbo builds would be premium; Either during the build or as an option to be excluded for the next build (why? -> I want to provide statistics before rolling the tool out, like "our builds will be 60% faster" without actually fixing all the problems the code has with jumbo builds)
• When editing the RudeBuild.config I can't exclude whole projects by hand because it's on a per file basis

[martinecker]

Thanks for your comments. I've had plans to address most of the things you mention and to essentially fully revamp the settings dialog as well as how the settings are stored, but I've just been too busy with other things to dedicate time to it. I don't use RudeBuild in my day-to-day work anymore and so I've not devoted much time in recent years developing it further. Pull requests are of course always welcome.