Closed JosuGZ closed 6 months ago
I believe it is because your GCC is too old, you need 10.3-2021.10. See https://github.com/InfiniTimeOrg/InfiniTime/blob/main/doc/buildAndProgram.md I can't speak for the dev container because I don't use it, but I suspect the compiler version is the problem
I'm seeing that there is a docker folder which looks similar to the .devcontainer folder. Perhaps the devcontainer should reverence the docker folder as it seems outdated.
The latest docker container also fails though :'( (Error: @swc/core threw an error when attempting to validate swc compiler options.
).
I can't see older images without signing to docker hub apparently.
See #1587 for the devcontainer.
I have ram overflow by 150iesh bytes on gcc-arm-none-eabi-10.3-2021.10
only on Debug builds. Removing the logging functionality seems to make it fit !
InfiniTime statically allocates most of the RAM memory and we check that the project builds with the version of the compiler we mention in the documentation (10.3-2021.10 as of now).
Building with another version of the compiler might change the way the memory is allocated and could indeed fail.
Also, building in debug mode with the logging feature enable will definitely allocate more RAM memory which will result in memory overflow at link time.
If you want to temporarily build in DEBUG and/or enable logging, you can reduce the size of the main memory heap by editing this constant. I regularly set configTOTAL_HEAP_SIZE
to 1024*35
when I enable the logging functionality.
Please not that this reduce the total amount of memory available to InfiniTime and the apps so this could trigger some issues in memory hungry apps.
Verification
What happened?
I'm trying to build the project but I get a RAM overflow on the linking step.
Reproduction steps
I'm using the dev container. Inside, I run the following commands (after installing node + some libs wich is another topic):
Output
Version
Latest commit on main.