Updating and building a C++ extension locally using PXT_FORCE_LOCAL=1 pxt build in the CLI works.
Building the same extension in the CLI using the cloud compiler via pxt build fails.
It shows the waiting 8s for C++ build... message multiple times and then it gives up with abandoning C++ build, terminating with this error:
error TS9043: The hex file is not available, please connect to internet and try again.
The thing we found odd is that in some cases, importing an extension as a C++ project into the MakeCode editor (via import of GH URL, or by drag&drop a locally built hex file) did successfully re-build the C++ code and produced a hex file.
However, creating a new project and adding the same extension using exactly the same tag, then building the new project does fail with the same abandoning C++ build error shown in the browser console.
Reproduce
This simple project is using a simple C++ extension pxt-banana to replicate the issue:
Description
Updating and building a C++ extension locally using
PXT_FORCE_LOCAL=1 pxt build
in the CLI works.Building the same extension in the CLI using the cloud compiler via
pxt build
fails. It shows thewaiting 8s for C++ build...
message multiple times and then it gives up withabandoning C++ build
, terminating with this error:The thing we found odd is that in some cases, importing an extension as a C++ project into the MakeCode editor (via import of GH URL, or by drag&drop a locally built hex file) did successfully re-build the C++ code and produced a hex file.
However, creating a new project and adding the same extension using exactly the same tag, then building the new project does fail with the same
abandoning C++ build
error shown in the browser console.Reproduce
This simple project is using a simple C++ extension pxt-banana to replicate the issue:
https://makecode.microbit.org/_FtsJVkTamUDr
Versions
Tested with MakeCode live:
And beta: