Build debug information alongside non-debug builds.

We should then be able to use it in Chrome's Wasm/DWARF debug tooling to
understand production issues.

Author: microbit-matt-hillsdon

Makefile

@@ -9,7 +9,7 @@ build:
 dist: build
 	mkdir -p $(BUILD)/build
 	cp -r $(SRC)/*.html $(SRC)/term.js src/examples $(BUILD)
-	cp $(SRC)/build/firmware.js $(SRC)/build/simulator.js $(SRC)/build/firmware.wasm  $(BUILD)/build/
+	cp $(SRC)/build/firmware.js $(SRC)/build/simulator.js $(SRC)/build/*.wasm  $(BUILD)/build/
 
 watch: dist
 	fswatch -o -e src/build src  | while read _; do $(MAKE) dist; done

src/Makefile

@@ -52,6 +52,8 @@ JSFLAGS += -s EXPORTED_RUNTIME_METHODS="['ccall', 'cwrap']" --js-library jshal.j
 
 ifdef DEBUG
 JSFLAGS += -g
+else
+JSFLAGS += -gseparate-dwarf
 endif
 
 SRC_C += \
@@ -148,4 +150,4 @@ simulator-js:
 
 include $(TOP)/py/mkrules.mk
 
-.PHONY: simulator-js
+.PHONY: simulator-js