bricks/simhub: Fix debug build paths and mpy-cross.

Then we don't end up with unexpected build files in the MicroPython submodule when debugging.

Author: laurensvalk

.vscode/launch.json

@@ -96,7 +96,7 @@
             "name": "simhub",
             "type": "cppdbg",
             "request": "launch",
-            "program": "${workspaceFolder}/bricks/simhub/debug/firmware.elf",
+            "program": "${workspaceFolder}/bricks/simhub/build-debug/firmware.elf",
             "stopAtEntry": false,
             "cwd": "${workspaceFolder}",
             "environment": [

.vscode/tasks.json

@@ -47,7 +47,7 @@
             },
             "label": "build simhub (debug)",
             "type": "shell",
-            "command": "poetry run make DEBUG=1 BUILD=debug COPT=-DPBDRV_CONFIG_CLOCK_LINUX -j",
+            "command": "make -C ../../micropython/mpy-cross -j && poetry run make DEBUG=1 BUILD=build-debug COPT=-DPBDRV_CONFIG_CLOCK_LINUX -j",
         },
         {
             "label": "build test-pbio",

Makefile

@@ -86,9 +86,7 @@ simhub: mpy-cross
 
 clean-simhub: clean-mpy-cross
 	@$(MAKE) -C bricks/simhub clean
-	@$(MAKE) -C bricks/simhub clean
-	@$(MAKE) -C bricks/simhub clean BUILD=debug
-
+	@$(MAKE) -C bricks/simhub clean BUILD=build-debug
 
 mpy-cross:
 	@$(MAKE) -C micropython/mpy-cross CROSS_COMPILE=$(HOST_CROSS_COMPILE)