If you've written a neat piece of software and you want everyone else to try it, my advice is to distribute it finished and ready to run. Don't do this twaddle where you put together a bunch of component files and some vague instructions on how to compile them, because the average user (or even the above-average user, like me) is not going to be able to do jack with this. At best, it's an annoying oversight... at worst, it's creepy gatekeeping, and that doesn't help anybody. (Especially not above-average users like me.)

Don't just assume that the user will know what to do with these files. Many will not know. And if you're not there to guide them through it, all that data is going to be about as useful to them as naked pictures of Estelle Getty. Seriously, offering a BASIC compiler on your Github and then expecting the people who want to program in BASIC to fight with C++ and a million different dependencies is some next level sadism. It's a carrot and stick situation, except you're hitting the user with the stick while feeding them the carrot from the opposite end.

To recap: never distribute software without compiling it first. What good does that do anybody? Looking at you specifically, Ulrich Hecht.