I will provide new 4klang.h and 4klang.inc files.

Example song with 4klang 3.11. With 4klang 3.11 export contains 4klang.h and 4klang.inc instead of 4klang.obj. Included yasm.exe compiles 4klang.inc to 4klang.obj.

In principle building everything in one go is a good idea, but I'm worried about maintaining the versioning properly for 4klang. In many cases the music is made by a separate party, and they might be using a different version of the synthesizer, producing .inc files that potentially lead to incomprehensible build errors, or worse, catastrophic runtime failures (been there).

For that reason I think it's ultimately preferable to try to always build the 4klang binary file separately, using only the sources found in its distribution package to avoid the cases above. This is how I feel about the topic for now anyway, but maybe I'll come around, so I'll heave this PR pending and open still.