Skip to main content
User1655833706281357277
Associate III
June 23, 2025
Solved

How to update path to GNU make in STM32CubeIDE on macos Sequoia, M2 processor

  • June 23, 2025
  • 1 reply
  • 324 views

I just installed the latest STM32CubeIDE 1.18.1 on a mac Studio M2 running Sequoia 15.5.  The default GNU make on the machine is /usr/bin/make, version 3.81.  The IDE is clearly creating makefiles for a later version of make, because building applications in the IDE errors out with "**** multiple target patterns" on a make rule that lists the elf and map files as targets.  I have make 4.4.1 installed via brew, but how to tell STM32CubeIDE where to pick it up is buried somewhere and I'm not seeing anything in any documentation.  Does anyone know how to fix this?

 

Best answer by User1655833706281357277

Here's what's going on for anyone working across macos and windows.   For reasons I still don't understand, Eclipse wants an absolute path to the linker file you're using.   On windows the path will look like "C:\Users\<path-to-project>" usually.  This gets stuffed into the .cproject file.  If you're trying to share projects and check in the .cproject file, the IDE on macos will read that linker file path into the project, which is not a valid path in macos.  It also puts the linker file on the dependency list in the makefile it generates.  It's the invalid linker path with backslashes in it that's generating the "*** multiple target patterns" error, not the two targets on the right side of the colon.   

So I guess it's impossible to share Eclipse projects across OSes without fixing up the .cproject file.

*sigh*

 

1 reply

User1655833706281357277
User1655833706281357277AuthorBest answer
Associate III
June 23, 2025

Here's what's going on for anyone working across macos and windows.   For reasons I still don't understand, Eclipse wants an absolute path to the linker file you're using.   On windows the path will look like "C:\Users\<path-to-project>" usually.  This gets stuffed into the .cproject file.  If you're trying to share projects and check in the .cproject file, the IDE on macos will read that linker file path into the project, which is not a valid path in macos.  It also puts the linker file on the dependency list in the makefile it generates.  It's the invalid linker path with backslashes in it that's generating the "*** multiple target patterns" error, not the two targets on the right side of the colon.   

So I guess it's impossible to share Eclipse projects across OSes without fixing up the .cproject file.

*sigh*