Closed the-maldridge closed 6 months ago
With 0.0.9 the problem occurs, but can be worked around by not using a tempdir for build.
$ gizmo firmware build --directory fw --preserve
Will work and the fw directory can be deleted after the command completes.
I attempted using the above command and it resulted in failure, Do you know a work around? If you do, it would be greatly appreciated.
`$ gizmo firmware build --directory fw --preserve
2024-02-14T10:45:27.196-0600 [INFO] firmware: Log level: level=info 2024-02-14T10:45:27.198-0600 [INFO] firmware.factory: Performing Step: team=91 step=Unpack 2024-02-14T10:45:27.206-0600 [INFO] firmware.factory: Performing Step: team=91 step=Configure 2024-02-14T10:45:27.206-0600 [INFO] firmware.factory: Performing Step: team=91 step=Compile 2024-02-14T10:45:29.204-0600 [WARN] firmware.factory: Halting build: error="exit status 1" 2024-02-14T10:45:29.204-0600 [ERROR] firmware: Build failed: error="exit status 1" `
I' need more information to debug this, starting with what version you have installed. You can also produce a more useful log by setting the LOG_LEVEL
environment variable to trace
, which will dump the verbose status from the compiler. Before you go down that route though, I'd suggest trying on the most recent build available today, which is 0.0.11-rc1.
This build worked (0.0.11-rc1) for us until Running a Practice Field Mode $ gizmo field practice 213
C:\Users\3d254\Documents\Gizmo>gizmo field practice 213 2024-02-14T13:35:32.699-0600 [INFO] field: Log level: level=info 2024-02-14T13:35:32.717-0600 [ERROR] field.gamepad-controller: Wrong joystick counts!: axis=7 buttons=10 2024-02-14T13:35:32.717-0600 [ERROR] field: Error initializing gamepad: error="bad joystick config"
Okay that's a different issue, but the short of it is that you have the switch on the bottom of the gamepad in the wrong position. It should be in 'D'.
Since this process has been significantly revamped I'm going to close this issue. Please open a new issue if you encounter issues compiling, or open a discussion if you need 1 on 1 help.
Initially it was determined that a missing dependency in the gizmo firmware would prevent successful compilation on windows PCs, further identified to be all builds affected. 0.0.8 was released to resolve this issue, but did not result in working windows systems.