Please file an issue with a testcase for SDL1 and 2 both being linked in, on e.g. browser.test_sdl2_jpeg I don't see that happen.
Regarding the linking debate, would using pkg-config be a solution that everyone is happy with? Using pkg-config is pretty standard stuff, and we could make it emit USE_SDL=2 etc. under the hood, as internal flags that users would never see. - Alon On Thu, Nov 6, 2014 at 2:31 AM, Mark Callow <[email protected]> wrote: > There are still some outstanding questions on this plus I have a new one. > > On 29/10/2014 11:46, Mark Callow wrote: > > ... I don't understand what you mean by "check the -L paths manually". > In most compile/link tools following a search path and using default > locations when nothing is found on them is a fundamental part of the > linker's task. Why so averse to having emlink do this? > > ? > > ... How does -S USE_SDL=2 allow you to build dependencies? > > ? > > I agree that automatic downloads greatly raise the cost of a mistake in a > -L specification. The solution is explicit downloading as suggested by > Brion and following standard compile/link practices, instead of inventing > something entirely new. > > I want to clarify that this cost of a mistake is not a reason to use the > -S USE_SDL=2 > > ... I thought libGLESv2 was built into the emsdk. Are you proposing > making it subject to automagic downloading? > > ? > > And the new question ... > > In the emsdk 1.22.0 I am currently using, the existing SDL 1.x is > included in the generated .js file even though my app is not calling it. > Will this be changed? I'd hate to continue having both SDL 1.x and SDL 2 > taking space. > > 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/d/optout. > -- 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/d/optout.
