6b3581bb6c
Use custom assembly resolver
...
Before, I was relying on a bit of luck that the resolver would
use the correct asms - now I make sure it does.
The build step will now fail if a resolution failure occurs -
this is better than runtime errors.
2018-04-25 15:46:01 -07:00
bb78f433e3
Bump linker
2018-04-25 15:45:37 -07:00
e94436c987
Update link to mono-wasm-a14f41ca260.zip
2018-04-19 21:10:43 +02:00
0e51219234
Update the wasm sdk to 108
...
Fixes #135
2018-04-18 18:18:04 -07:00
931cb7126d
Make SDK installation more robust
...
Fixes #120
2018-04-16 14:40:46 -07:00
d7d7290c87
Don't link the main assembly
...
The main assembly was getting marked to link because it is an EXE.
This was making data binding fail.
Fixes #113
Fixes #107
2018-03-23 14:38:08 -07:00
865929c434
Turn linker resolution errors into warnings
2018-03-23 13:58:29 -07:00
794e27dd79
Add charset to wasm HTML
2018-03-13 16:49:21 -07:00
b615e7d6d7
Find Ooui.dll even if it's linked out
2018-03-13 16:04:31 -07:00
b45015541b
Fix build dist paths
2018-03-13 15:58:18 -07:00
95adaad77c
Use server.py from wasm sdk
2018-03-13 14:03:46 -07:00
a1dab5fc06
Use the Cecil included with the linker
2018-03-13 13:46:34 -07:00
7d70351418
Add linker to wasm build task
2018-03-13 13:16:59 -07:00
664bcbb8ec
Fix JS load order
2018-03-13 10:21:08 -07:00
c41057a634
Run the correct entrypoint
2018-03-13 10:05:43 -07:00
d4308a740d
Implement the wasm build task
2018-03-13 00:59:33 -07:00
82a154b1e2
Add scaffolded wasm build task
2018-03-12 22:27:03 -07:00
Frank A. Krueger
Alexander Köplinger