Closed rabarar closed 8 months ago
The wio-e5
environment is still a work-in-progress, see #2960.
Do you need specifically this environment? While this is set as the default_envs
in platformio.ini
, you can select the appropriate environment for your device.
Is there a stable branch to pull?On Jan 4, 2024, at 10:34 AM, GUVWAF @.***> wrote: The wio-e5 environment is still a work-in-progress, see #2960. Do you need specifically this environment? While this is set as the default_envs in platformio.ini, you can select the appropriate environment for your device.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
For the wio-e5
environment or in general? The firmware should build successfully for all supported devices on the master
branch as can be seen by the CI.
As I said, the wio-e5
is a work-in-progress in PR 2960 using branch stm32wl
.
I’m confused then. I simply cloned the repo master branch, made no modifications, and attempted to build it. So I don’t see how your CI is successful when I can’t replicate a clean, unmodified build.On Jan 4, 2024, at 12:55 PM, GUVWAF @.***> wrote: For the wio-e5 environment or in general? The firmware should build successfully for all supported devices on the master branch as can be seen by the CI. As I said, the wio-e5 is a work-in-progress in PR 2960 using branch stm32wl.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
I’m confused then. I simply cloned the repo master branch, made no modifications, and attempted to build it. So I don’t see how your CI is successful when I can’t replicate a clean, unmodified build.On Jan 4, 2024, at 12:55 PM, GUVWAF @.> wrote: For the wio-e5 environment or in general? The firmware should build successfully for all supported devices on the master branch as can be seen by the CI. As I said, the wio-e5 is a work-in-progress in PR 2960 using branch stm32wl. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.>
You need to pick your build target before building. That said, it's a problem if we're building a WIP target by default.
We've switched the default build target back to the T-beam. This should make the firmware build cleanly for that device, without setting the target, so closing this issue. Thanks for pointing out this unintended behavior!
My pleasure!On Jan 4, 2024, at 1:24 PM, Jonathan Bennett @.***> wrote: We've switched the default build target back to the T-beam. This should make the firmware build cleanly for that device, without setting the target, so closing this issue. Thanks for pointing out this unintended behavior!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
Category
Other
Hardware
Not Applicable
Firmware Version
latest pull
Description
The firmware doesn't build: the
c_cpp_properties.json
generated file is corrupted with escape\
characters for one of the filenames"~/.platformio/packages/framework-arduinoststm32/variants/STM32WLxx/WL54CCU_WL55CCU_WLE4C\(8-B-C\)U_WLE5C\(8-B-C\)U",
The build fails with errors:
Relevant log output
No response