include all "interlinked" files into 1 bmx and include that bmx into your project ... and never build sources that are part of that package on their own, always only the page.
Yeah, that's what I decided to do - make a 'framework' .bmx file and package it all together.
It's just, some of the files that are included have no other dependencies - and while not necessary it would be ideal to be able to conditionally (somehow) make them 'strict' when I just want to test some new added code quick. Compiling the whole framework seems like a clunky fix - but it works so meh.
All in all, I still much prefer the small taste of blitz that I've had compared to the small taste of C++. :)