Static linking of bitcode still works. You can certainly deliver a library in bitcode format that people receive and link with their project, or just build multiple libraries in your project as bitcode (.so, .a, .o, etc.) and link those statically then convert to JS, etc.
What does not work is linking done *after* conversion to JS: dynamic linking or dlopen of JS files. (Those work to some degree in the old compiler, but not in fastcomp, until we figure out our plans there.) - Alon On Mon, Feb 24, 2014 at 8:37 PM, Mark Callow <[email protected]>wrote: > On 2014/02/21 10:17, Alon Zakai wrote: > > Perhaps the biggest missing thing is linking support. This is not > deprecated, but there are some issues with it - it works on C code, but C++ > can break it. For that reason we may want to reconsider our linking > approach, so there is no point adding that to fastcomp before doing so. > Also, linking is less crucial for fastcomp anyhow - linking has been a way > to avoid rebuilding big projects, but fastcomp is fast enough to rebuild > entire projects anyhow, and full rebuilds will give more optimal results > due to the compiler seeing all the code together and putting it all in one > asm.js module. > > I'm not entirely sure what you mean by linking support so the following > may not be relevant. > > Build time is not the only reason for not wanting to build entire projects > together. > > When creating an Emscripten config from an existing MSVS solution that is > configured as multiple projects (e.g. a library and several applications) > you want to retain the structure. I have such a solution currently using > the old compiler. There the library build generates bitcode. As I > understand it, the application compiles generate JS for the library and > application. > > One may want to deliver a library for people to use without providing its > source code. The bitcode file would work for this too. > > Regards > > -Mark > -- > 注意：この電子メールには、株式会社エイチアイの機密情報が含まれている場合が有ります。正式なメール受信者では無い場合はメール複製、 > 再配信または情報の使用を固く禁じております。エラー、手違いでこのメールを受け取られましたら削除を行い配信者にご連絡をお願いいたし ます. > > NOTE: This electronic mail message may contain confidential and privileged > information from HI Corporation. If you are not the intended recipient, any > disclosure, photocopying, distribution or use of the contents of the > received information is prohibited. If you have received this e-mail in > error, please notify the sender immediately and permanently delete this > message and all related copies. > > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
