If I write a bunch of pure B4X code in a bunch of modules, I can choose "Compile to Library" in the B4J IDE and that resulting library will run on B4A (with a little hacking), provided there's no JVM-specific code. It won't run on B4i. However, there's no reason why it can't run on B4i. It is, after all, pure B4X code. I could import all those modules individually into a B4i project and run them. But this is cumbersome and error-prone.
A better solution would be to create a new compilation option called "Compile to B4X Library" that will compile a bunch of B4X class or static code modules into a zipped package that can then be distributed, stored in B4J/A/i Additional Libraries folders and read by the B4J/A/i IDEs where it will be treated just like a normal library for that platform.
A better solution would be to create a new compilation option called "Compile to B4X Library" that will compile a bunch of B4X class or static code modules into a zipped package that can then be distributed, stored in B4J/A/i Additional Libraries folders and read by the B4J/A/i IDEs where it will be treated just like a normal library for that platform.
Last edited: