The additional libraries folder can be organized in a way that allows sharing cross platform libraries between B4A, B4J and B4i. From now on, the recommended way to organize the additional libraries folder: Additional libraries folder is set under Tools - Configure Paths. As you can...
I'm afraid that this will be a problem.
The b4xlib developers MUST clearly define for what platform the given library is dedicated.
BUT, in my opinion, b4xlibs MUST be valid for all three platforms!!!
Otherwise it will become a jungle and everybody will be lost!
If any, so called b4xlib, is not valid for all three platforms it should have another suffix.
Well, that's my opinion.
I'm afraid that this will be a problem.
The b4xlib developers MUST clearly define for what platform the given library is dedicated.
BUT, in my opinion, b4xlibs MUST be valid for all three platforms!!!
Otherwise it will become a jungle and everybody will be lost!
If any, so called b4xlib, is not valid for all three platforms it should have another suffix.
Well, that's my opinion.
Currently the IDE only reads the manifest file when a library is selected. It will show an error message when an unsupported library is selected.
b4xlibs have all kinds of advantages (and also some disadvantages) over compiled libraries. Their use case is definitely not limited to cross platform libraries.