Just playing around with C++ extensions. I made a dummy C++ extension, but cannot build it from the command line - I made sure my CPP file is in the pxt.json file, and made sure that it contains a compile error, but “pxt build” does not attempt to build it.
Targetting microbit works, for example. I can set up the same project, by running “pxt target microbit”, and that will dispatch the .cpp file to the cloud build as I expect. But “pxt target arcade” fails, because pxt-arcade is not visible to npm’s directory?
So if I run “pxt build” in this directory without previously targetting microbit, the build will succeed (because my *.ts files are empty, and valid), but does not attempt compilation of the C++ source.
Is there a way of overriding this locally? I’ve tried cloning the pxt-arcade repo locally, but can’t figure out what to give to “pxt target” to make it look at the local copy - it always seems to hit the online directory of pxt targets, and cant find ‘arcade’.
I can compile the extension, including it’s C++ files in the online editor. And the build fails as expected, but it’s not possible to see the errors, so this isn’t a great write-compile-test experience.
How are other folks doing this?