On Tue, Oct 28, 2014 at 2:27 PM, Jukka Jylänki <[email protected]> wrote:

>
> I somewhat dislike the current behavior of -s USE_SDL2=1 at link time for
> downloading and building SDL2 on demand. This is because the scheme does
> not feel scalable. What should we do with other potential libraries like
> FreeType and Regal and zlib and other common ones that people are using?
>

I'm not sure why you feel this is not scalable? It would take literally
just a matter of minutes to add e.g. zlib to emscripten-ports: make the
repo on github, upload the content, write a short tools/ports/zlib.py
script that builds it, add an option to settings.js (USE_ZLIB), and we're
basically done. The amount of work is basically minimal - I don't see how
any of those steps just mentioned could be removed.

If people want zlib, freetype, regal, etc., let's just add them. Happy to
do it myself, just not sure which libraries people want. (Regarding regal,
it doesn't work last I checked, so that's a different issue.)


>
> For linking to the built-in provided src/library_x.js files, I'm leaning
> on removing the current autolinking support to any of these, but how about
> if we dropped the --js-library and instead did "-lglut.js" ("-lsdl.js" and
> so on) to mean to link to the file "library_glut.js" that should exist
> somewhere in the filesystem in the -L paths (searching $EMSCRIPTEN/src as
> last one)? The suffix .js to -l would make it explicit that one is looking
> to link to a library_x.js file. That would be a more consistent way instead
> of adding heuristics that "-lGLESv2 should map to library_gl.js, -lGLUT
> should map to library_glut.js, -lal, -lsoft_oal should map to
> library_al.js, ..." and so on.
>

On the one hand I like this. On the other hand though, it's a big change
for users, and I worry about inconveniencing them for this.

- Alon

-- 
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.

Reply via email to