Hi everyone,
I'm using MCUXpresso 24.9.
For some reasons in my project I needed to chnge the compiler command line. The chenges are working fine, the project is built without problem.
But there is a side effect: the indexer is not able to resolve lib include files:
To debug the problem I created a test program with the default options (New Project -> Create a new C/C++ project), then I changed the command line to compile the project (Project properties -> C/C++ Build -> Settings -> MCU C compiler) from the default value ("arm-none-eabi-gcc") to "../compile.cmd":
The file compile.cmd is located in the project directory and contains the single line:
arm-none-eabi-gcc %*
If I compile the program the process is terminated without errors, but all the c library files are highlighted as unresolved inclusions: so the problem belongs only to the indexer.
When there is the default setting no highlight is present and in the <WorkspaceDir>\.metadata\.log file there are the following messages:
!ENTRY org.eclipse.cdt.core 1 0 2024-10-14 10:30:17.365
!MESSAGE Indexed 'MIMXRT1064_Project' (20 sources, 43 headers) in 1,87 sec: 8.359 declarations; 17.870 references; 0 unresolved inclusions; 0 syntax errors; 0 unresolved names (0%)
While when there is my custom setting there are the following messages:
!ENTRY org.eclipse.cdt.core 4 0 2024-10-14 10:32:13.001
!MESSAGE Error: Cannot run program "..\compile.cmd": Launching failed
!STACK 0
java.io.IOException: Cannot run program "..\compile.cmd": Launching failed
at org.eclipse.cdt.utils.spawner.Spawner.exec(Spawner.java:450)
at org.eclipse.cdt.utils.spawner.Spawner.<init>(Spawner.java:147)
at org.eclipse.cdt.utils.spawner.Spawner.<init>(Spawner.java:134)
at org.eclipse.cdt.utils.spawner.ProcessFactory$Builder.start(ProcessFactory.java:273)
at org.eclipse.cdt.utils.spawner.ProcessFactory.exec(ProcessFactory.java:366)
at org.eclipse.cdt.core.CommandLauncher.execute(CommandLauncher.java:189)
at org.eclipse.cdt.internal.core.BuildRunnerHelper.build(BuildRunnerHelper.java:274)
at org.eclipse.cdt.managedbuilder.language.settings.providers.AbstractBuiltinSpecsDetector.runProgramForLanguage(AbstractBuiltinSpecsDetector.java:808)
at org.eclipse.cdt.managedbuilder.language.settings.providers.AbstractBuiltinSpecsDetector.runForLanguage(AbstractBuiltinSpecsDetector.java:736)
at org.eclipse.cdt.managedbuilder.language.settings.providers.AbstractBuiltinSpecsDetector.runForEachLanguage(AbstractBuiltinSpecsDetector.java:601)
at org.eclipse.cdt.managedbuilder.language.settings.providers.AbstractBuiltinSpecsDetector$1.runInWorkspace(AbstractBuiltinSpecsDetector.java:527)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:43)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
!ENTRY org.eclipse.cdt.core 1 0 2024-10-14 10:32:14.602
!MESSAGE Indexed 'MIMXRT1064_Project' (20 sources, 30 headers) in 1,05 sec: 7.246 declarations; 12.921 references; 18 unresolved inclusions; 59 syntax errors; 3.440 unresolved names (15%)
How can I try to remove the problem?
Many thanks
Biafra
Hi @Alice_Yang,
Now I'm able to configure an absolute path depending on the project localtion. It need to use the ProjDirPath path variable, as on this image:
However, the real project is a very complex project and the command line exceeds the 8191 character limit, so I cannot use the Windows .cmd batch file.
Because Git is installed on my PC, I can use a .sh shell file.
The file compile.sh is located in the project directory as compile.cmd and contains the following lines:
#!/bin/sh
arm-none-eabi-gcc $@
Although with compile.sh file the project is built with no errors, using a .sh file leads to the same problem: the indexer is not able to resolve lib include files.
Many thanks
Biafra
Hi @Alice_Yang,
Is there any news regarding the problem I reported?
Has it been verified from the development team?
In the meantime I switched to MCUXpresso 25.6, but nothing is changed.
Despite the error reported on the problems view, the project compiles fine.
Many thanks
Biafra
