Hi Alon,

Just test driving the new 1.16.0 Emscripten portable SDK on the Mac. When I 
run Ammo's make.py, I get:

Will-Eastcotts-Mac-mini:ammo.js willeastcott$ python make.py 

--------------------------------------------------
Building ammo.js, build type: ['-O3', '--llvm-lto', '1', '-s', 
'NO_EXIT_RUNTIME=1', '-s', 'AGGRESSIVE_VARIABLE_ELIMINATION=1', '-s', 
'TOTAL_MEMORY=67108864']
--------------------------------------------------


==========================
Stage 1: Generate bindings
==========================

python: can't open file 
'/Users/willeastcott/Documents/Dev/emsdk_portable/emscripten/1.16.0/tools/webidl_binder.py':
 
[Errno 2] No such file or directory
Traceback (most recent call last):
  File "make.py", line 80, in <module>
    assert os.path.exists('glue.js')
AssertionError


Indeed, it seems that webidl_binder.py isn't in the tools folder, even in 
the master emscripten repo. Am I missing something here?

Thanks!

On Thursday, 24 April 2014 02:02:40 UTC+1, Alon Zakai wrote:
>
> There is a new tool for gluing together C++ and JS, the WebIDL binder,
>
> https://github.com/kripken/emscripten/wiki/WebIDL-Binder
>
> Details are in that link.
>
> I've been testing the tool on ammo.js (port of bullet), along with a major 
> update of ammo to latest upstream bullet and latest emscripten. See an 
> update here
>
> https://github.com/kripken/ammo.js/issues/60
>
> In particular, we need help from people using ammo.js to test the new 
> build and add the interfaces they want to be bound, as the new bindings 
> generator requires an IDL file to declare what is actually bound (see 
> details in that link, and the previous one). Basically, the new approach 
> will lead to smaller and faster builds, but the IDL files need to be 
> written; the current file has everything needed for the ammo test suite and 
> the WebGL demo.
>
> - 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