I think (but I'm not totally sure) it would be feasible to link the modules' .a files into your C/C++ executables, but presumably a lot of work to wrap the functions, types, etc on the C/C++ side. I actually had a little go at this last night with a really simple function and DevCPP but failed miserably.
Licensing-wise I can't see any real difference between BlitzMax calling gcc to link the .a files into executables and someone doing it 'manually', or from their C++ IDE. Distributing the libraries separately would be a definite no-no, of course.
I can't imagine Mark would go out of his way to make things C/C++ friendly, or deliberately unfriendly for that matter -- he's writing for Blitz, of course.
Licensing-wise I can't see any real difference between BlitzMax calling gcc to link the .a files into executables and someone doing it 'manually', or from their C++ IDE. Distributing the libraries separately would be a definite no-no, of course.
I can't imagine Mark would go out of his way to make things C/C++ friendly, or deliberately unfriendly for that matter -- he's writing for Blitz, of course.