platform: moved from arm-none-eabi-gcc 10.3.1-2.3 to 12.2.1-1.2 #1944
Conversation
See: https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/releases/v12.2.1-1.2 Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
due to newlib version 4.2.0 provided within arm-none-eabi-gcc-12.2.1 See: https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git Title: In <stdio.h> provide only necessary types Commit: 357d7fcc6ad1b0660e2b3131d09eb22e2559e46d Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
due to binutils version 2.39 provided within arm-none-eabi-gcc-12.2.1 Enabled by default since this version. Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
fpistm
force-pushed
the
xpack_gcc_12.2.1-1.2
branch
from
bb4f3f0
to
cfa31c0
Compare
|
If I understand your index.json file correctly, you provide support for multiple toolchain releases, including the latest 12.x. Any reasons for not also including the 11.x? At least the latest v11.3.1-1.1.2? |
|
Toolchain is linked to a release so next one will be with v12. |
|
Your index.json lists the following:
I confess that I don't know how this file is used, but if users can select any of the above releases, I think they should also be allowed to chose "11.3.1-1.1", even if the latest one is "12.2.1-1.2". |
|
No user could not select the toolchain. The release give their tools dependencies. |
I see. But then why are those old definitions still present in the JSON file? |
Because all release are available. User select the core version and then tools dependencies are selected. |
|
To go further, the .json provides all information to install a specifc core version. So 2.0.0 request to have gcc version 9.3.1-1.3 For the next 2.5.0, the 12.2.1-1.2 will be required. |
|
I'm not familiar with the Duino versioning scheme, and I don't know how much freedom you have with your releases, but, from the toolchain point of view, it is useful to have the choice to build a project with a specific version. Can you go back in time and insert an intermediate release, like 2.4.x, configured with GCC 11.3? Or make 2.5.0 with 11.3, and 2.5.1 with 12.2? |
|
Honestly, I see no reason for doing this nor the interest. |
devbranch of stm32duino/BoardManagerFiles updated to references the new toolchain used by CI:https://raw.githubusercontent.com/stm32duino/BoardManagerFiles/dev/package_stmicroelectronics_index.json
Deprecation notices
32-bit support
Support for 32-bit Intel Linux and Intel Windows was dropped in 2022. Support for 32-bit Arm Linux (armv7l) will be preserved for a while, due to the large user base of 32-bit Raspberry Pi systems.