Sorry for the long silence, I had a family health problem which had me away from home and with only access to email, no upload or download. Now that I am back I will be able to get on with the build-system updates, once I remember where I was up to ;-). Since I stuffed up copying the source to my laptop nothing has happened in the interim.

As I remember we were trying to come to a conclusion about commands for header files for C and C++ which are currently explicitly prevented from performing any compile or build.

The C++ work I have done in the meantime has re-inforced my desire to be able to at least compile C++ headers by themselves to get out the syntax typos because they tend to cause a lot of "flow on" errors in the .cpp file and C++ generates such enormous error messages (see http://www.parashift.com/c++-faq-lite/templates.html#faq-35.17 for an example). Also I have noticed that Geany 0.15 is very slow when there are lots of errors, maybe the regex parse is a bit slow, anyway that just makes it more important to compile the .hpp file first.

The question seems to be how we handle having different commands for the header files (different to the .cpp files that is) without creating new filetypes for them.

My last proposal was for a "variant" of the filetype which allowed different commands. The variant was identified by a subset of the filetypes extensions. This is a slightly general solution configurable in the filetypes or preferences files, or another option is something hard coded specifically for header files, not my favourite :(.