-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build_project.py broken under Windows. #81
Comments
If I try to run the command in subprocess separately, which I think is this one:
I get this information:
|
Found what triggered that error, turns out that even if slc is installed and in the path, the script needs to specify that the command to be executed is |
Windows isn't really a supported platform. We rely on GNU Make to build the resulting project so if you don't have it, either install it or run the tools via WSL. |
I can see that, because in the generated Makefile I see there are some calls to uname, which is not available in MS Windows. So, I solved the make "problem" by issuing |
I managed to get something functional, but instead of using WSL and reinstalling all the tools I had already set up, I used MSYS2 and added its binaries to the system path. This allowed me to run the build script up to the point where it calls the script to generate the GBL file, which fails due to some improperly escaped paths. However, when I manually run the GBL generation script, it successfully creates a GBL file that is recognized by the Universal Silabs Flasher and also by the Home Assistant configurator when flashed. Now, I just need to figure out what's causing the issue with the incorrect paths. |
I wanted to share how I managed in the end. And maybe it helps as reference for someone that has the system already setup in Windows and does not want to mix with more tools. I installed MSYS2 by issuing After that, I made some adjustments in Here’s the revised post-build command I implemented:
The command I am using to run it is:
And that works smooth. Once that said, this is more like a workaround that a proper solution to make it running in MS Windows. So whoever is in charge of issues, do with this information whatever you want. |
Just follow the steps described in the README. When trying to build the firmware, I have got this error:
The command called is:
The text was updated successfully, but these errors were encountered: