Closed NW-Lab closed 1 year ago
Is it a problem of Plugin?
I don't think so:
"moddable_manifest": { "include": "$(NODEREDMCU)/nodes/mcu/i2c/manifest.json" },
in combination with
creates .//nodes/mcu/i2c/manifest.json
... which is the erroneous path definition you can spot in your screencopy of the debug panel: It begins with .//nodes/...
@NextWorldLab – thank for the report and apologies for the trouble. And thank you @ralphwetzel for the quick attention.
It looks like the problem may be in how mcconfig is processing the relative definitions in the BUILD section of the manifest. That's a new feature and it looks like I may have gotten the handling of slashes wrong.
I don't have a Windows machine available right now to test, but I tried a quick fix. Maybe you can try running it? If not, we can test on Windows in the next day too. Here's the change. In $MODDABLE/tools/mcmanifest.js change the implementation of the parseBuild function to this:
Then you'll need to rebuild tools:
cd %MODDABLE%\build\makefiles\win
build
Then you can try rebuilding with the MCU plugin.
@phoddie san, @ralphwetzel san Thank you for your response.
It worked fine by modifying parseBuild.
Thanks,
Thank you for the quick confirmation! We will get that fix into a release as soon as we can.
I don't know if the ISSUE in the repository here is okay.
I can no longer build with the Node-RED MCU Plugin. Building on the command line is fine. The error message is "### Error: '.\nodes\mcu\i2c\manifest.json': manifest not found!"
manifest.json automatically generated by plugin
Is it a problem of Plugin?
thanks,