For now BMK tries to run "pre.bmk" before compilation and "post.bmk" after compilation.
Sometimes you have multiple "tools" in a single folder (forwhatever reason) or you might have different "main files" doing small adjustments (demo, release, test...).
To avoid having all these files use the same "pre.bmk" or "post.bmk" it would be a simple but handy addition to BMK to support "mysourcefile.pre.bmk" and "mysourcefile.post.bml".
For now BMK tries to run "pre.bmk" before compilation and "post.bmk" after compilation.
Sometimes you have multiple "tools" in a single folder (forwhatever reason) or you might have different "main files" doing small adjustments (demo, release, test...). To avoid having all these files use the same "pre.bmk" or "post.bmk" it would be a simple but handy addition to BMK to support "mysourcefile.pre.bmk" and "mysourcefile.post.bml".