arm-none-eabi-gcc and arm-none-eabi-g++ not found in PATH even though the folders are in PATH

[felixd]

Hello,

I am currently using MCUXpresso IDE v11.5.0 [Build 7232] [2022-01-11] and I have trouble solving 2 of the errors that are displayed in the IDE:

The last error is something I don't need to solve.

For the Resource called mcu-sw, the executables are found in the folder with the following path:

[...]\mcu-sw\Buildmanagement\Tools\GNU Tools Arm Embedded\9 2019-q4-major\bin

For this project, here are the current settings:

PATH: [...]\mcu-sw\Buildmanagement\Tools\GNU MCU Eclipse\Build Tools\2.12-20190422-1053\bin;[...]\mcu-sw\Buildmanagement\Tools\GNU Tools Arm Embedded\9 2019-q4-major\bin;C:/nxp/MCUXpressoIDE_11.5.0_7232/ide/jre/bin/server;C:/nxp/MCUXpressoIDE_11.5.0_7232/ide/jre/bin

Toolchain setting:

Arm Toolchains Paths:

Global Toolchain settings:

Workspace toolchain settings:

The project (which is a C project) still compiles and outputs a binary file even though these errors are present, so the gcc.exe executable must be found somehow by the IDE even though it says it is not in the PATH.

What should I do to remove these errors?

Thank you for your help,

Félix D.

[ErichStyger]

You have to keep in mind that the 'MCUXpresso SDK project' is different from a 'CDT' or 'GNU MCU' project. You can see this with the MCU settings:

So it all depends what kind of project you have created. It sounds you created it as GNU MCU Eclipse project, and then you do not have that linkage to the SDK and manifest file (as noted in your last error message). So you project will compile (based on your project settings and where it finds the GNU tools), but it is fundamentally different from the MCUXpresso SDK based project.

You can do the one or the other, and it is basically your design decision, which route you are going. For example you can use a make or Cmake based project too (I just wrote about this here: https://mcuoneclipse.com/2022/09/04/tutorial-creating-bare-bare-embedded-projects-with-cmake-with-ec... )

I hope that makes sense?

[felixd]

Thank you for your quick reply, it makes sense and helps me understand the IDE a bit better.

To be clear, there are currently two projects that are triggering errors in my MCUXpresso IDE: the "bootloader" project, which was aborted and is not being used anymore. This project triggers an error because its has no linkage to an SDK but since it was dropped I don't really mind if it creates some errors.

The other one is the "mcu-sw" project, which triggers the first and second errors. This is the project I am currently working on and to which all the above project properties correspond. The two errors linked to that projects are the ones that I would like to solve.

[ErichStyger]

Maybe you could share the .project and the .cproject files of the project in question?

[felixd]

Sure! Here they are:

[ErichStyger]

Unfortunately, I cannot see all the information, because you seem to use a different plugin:

Interestingly, you actually do have SDK information present in that project:

Looking closer at the two messages you have, they are coming from from the Providers here (not sure, as your screenshot does not show the full message?):

[felixd]

Hi again!

Please find attached the full description of the two errors:

The command to get compiler specs is the following for the CDT Arm Cross GCC Built-in Compiler:

${COMMAND} ${FLAGS} ${cross_toolchain_flags} -E -P -v -dD "${INPUTS}"

Is there a mistake in this command?

I talked about this problem with one of my colleagues and he figured that the issue could come from the language settings file. The project triggers no error on his PC so he sent me a copy of his language settings. Here is a comparison of my file and his file (his file is on the left, mine is on the right):

Do you think this difference could be the reason why this error happens?

This colleague also mentioned that he used one of your articles to setup the project when the company was starting and the project was created. Thank you for your help!

[ErichStyger]

Yes, that difference could cause the messages. You could try to replace the &quot with "

Another approach would be to delete the .settings and re-open the project: the files should be restored (that's why I do not store the .settings folder in a VCS, but there has been some debate about this in the past in other places).

[felixd · Accepted solution]

Replacing the changes in the language settings and deleting completely the .settings folder was unsuccessful, but I clicked on "Restore Defaults" in the language settings provider options of the CDT Arm Cross GCC Built-In Compiler settings and the errors have disappeared, even though the command to get compiler specs and the other options remain the same.

Thank you very much for your help!