It works by inspecting only the actual source-code in your current working directory to determine:
and may even guess a suitable name for the resultant executable binary. It will write down this information as a Unix makefile and then run through the makefile, compiling the project using GCC. Once that finishes, Supermake will execute the binary. It is that simple, and can be thought of as doing to a pile of .c's and .cpp's what the Ruby or Python interpreters do to a pile of .rb's and .py's in terms of ease of use.
Requires Linux (Win & Mac support forthcoming) and a capable build environment. (sudo apt-get install build-essential should do it if you are on Ubuntu)
But, take note, Supermake's reliance upon the guessing and heuristics necessary to bandage this pain-point of C and C++ make it sadly unsuitable for more involved projects' build requirements. If you have multiple build targets, use obscure libraries, or employ a complicated directory structure, Supermake won't suffice. But for simpler build requirements, Supermake will soar.