That works, thank you very much. On Sunday, February 16, 2014 12:31:11 PM UTC-8, Alon Zakai wrote: > > Ok, done, see > > > https://github.com/kripken/emscripten/commit/153f2d93520f37525f30a3808b969c5533387a3c > > - Alon > > > > On Fri, Feb 14, 2014 at 5:36 PM, Joel Croteau <[email protected]<javascript:> > > wrote: > >> C would be preferable. >> >> >> On Friday, February 14, 2014 5:20:17 PM UTC-8, Alon Zakai wrote: >> >>> The downside is it would add a few K to the generated code size to >>> retain all the settings. So we would have to have this as an option I guess. >>> >>> Would it be convenient to access this data from JS, or from C? >>> >>> - Alon >>> >>> >>> >>> On Thu, Feb 13, 2014 at 6:27 PM, Joel Croteau <[email protected]> wrote: >>> >>>> That would be a very useful feature. My particular use case is in >>>> testing whether client-side arrays are available for a GLES2 application >>>> to >>>> use, so having some way to know whether FULL_ES2 was used would work well. >>>> >>>> >>>> On Thursday, February 13, 2014 2:19:21 PM UTC-8, Alon Zakai wrote: >>>> >>>>> There is no option for that now. We could add it if that would be >>>>> useful though. >>>>> >>>>> - Alon >>>>> >>>>> >>>>> >>>>> On Thu, Feb 13, 2014 at 10:55 AM, Jukka Jylänki <[email protected]>wrote: >>>>> >>>>>> Currently I'm not aware of such a feature. You could do a custom JS >>>>>> library that checks the values of the particular settings from >>>>>> src/settings.js and logs them, as those are not embedded to the >>>>>> generated >>>>>> executable for runtime examination. >>>>>> >>>>>> >>>>>> 2014-02-13 20:03 GMT+02:00 Joel Croteau <[email protected]>: >>>>>> >>>>>> Is there a way to determine, at compile time or at run time, what >>>>>>> settings were used when building the JavaScript file. For instance, is >>>>>>> there a way to test whether a program was built with FULL_ES2 enabled >>>>>>> or >>>>>>> not? >>>>>>> >>>>>>> -- >>>>>>> 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. >>>>>> >>>>> >>>>> -- >>>> 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] <javascript:>. >> 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.
