clibs source, integrity and building
Currently substrate downloads the clibs (clibraries.zip) from https://download2.gluonhq.com/substrate/clibs/${osarch}.zip and I have been wondering how (and from what sources) these libs were actually build and how I could reproduce building these particular libs for IOS and Android. Is there any documentation on this?
Also, it would be nice if these external files could be checked by the SubstrateDispatcher to be sure they have not been messed with (fingerprint and/or signature).
I'm asking same question for https://download2.gluonhq.com/substrate/staticjdk/
Sorry for double comment, but I really need answer to this issue. @jperedadnr maybe you can explain how to build those static libs ?
I managed to build a static JDK for iOS thanks to Multi Os Engine community.
In case someone else want to be able to build a jdk for ios, here is a repo to do so.