Can't build (custom) web interface #45
Comments
|
you did run the Normally Do you get any files in your dist folder at all? And how does your command line output look preceding the error message? |
|
Thanks for the speedy response, most appreciated. Here's the output from
The output from
The Many thanks for any insights you can give! |
|
Can you remove the node_modules folder, and retry with |
|
I removed node_modules, and re-ran as above - legacy flag required again, same output as above. I switched to a Ubuntu machine, and tried to compile one of the examples - it works, but there is an error from Sconscript:
And indeed, the So I think there's something wrong with the brew/npm environment on the Mac, and platformio behaves differently between mac and linux platforms resulting in a broken build under linux? I will experiment further with the linux environment to see if I can hack a build that correctly applies preBuild.py |
|
Ha! I think I have made some progress. The root cause of the problem may lie in the use of spaces within the library name "ESP8266 IoT Framework". Creating a symbolic link from
which does of course exist, but needs presumably to be correctly escaped to handle the spaces. Is that a major re-factor? |
|
Sorry, for all the issues you are facing, and thanks for your patience. To make sure it is due to the space in the library name: Can you try to:
In this case you use the project as a main project, and not as a platformio library. This should remove the spaces in your path. There is also work ongoing to make this library compatible with the ESP32 after which a name change will be needed anyway. At this point I will also remove the spaces from the name if this indeed causes the issue on mac :). As for you linux machine. If your platformio version is really 2.1.3 you should upgrade, that seems like quite an old version. Hopefully this will resolve the missing library folders. |
|
Success - under Ubuntu:
PS. Given that .pio isn't under source control by default, and github libraries do come and go over time, I think this method is to be preferred over the use of lib_deps because the code can be rebuilt from just the local git repo if required? Feel free to reuse any of above as you may wish, many thanks for the help. |
|
Glad that you got it working. Although in this way you lose some of the convenience benefits of PlatformIO of course ;). PlatformIO is actually there to do the configuration management, but indeed with your method you have everything fully local and you can employ your own strategies for managing the libraries. |
I ran into this same issue, maybe something changes in the way PlatformIO downloads dependencies. I will reopen this issue and investigate. |
|
See this discussion: platformio/platformio-core#3730 |
|
fixed in 9d36648 |
I've followed the instructions closely. I'm building on a Mac fwiw (I had to fix some paths to work in the unixy way, no biggie), and a fresh repo builds fine. I think this is a really exciting project, with the potential to be a fantastic time saver.
The trouble comes when I try to
npm run build-- I get errors regardingThis seems to be a failure of
webpack.config.jsassuming this file exists; I'm no npm expert and I can't see how/where index.html.gz might be generated.Manually creating a file with a copy of the standard index.html doesn't help - it resolves the error only to fail later with:
... and I am at a loss as to how to resolve this (believe me, I've tried!) because I'm unfamiliar with npm and friends.
Building from command line or with -D options both give similar results.
Any ideas, please?
The text was updated successfully, but these errors were encountered: