Which STM32Cube apps use these shell profile configurations on macOS

[callsignhermit]

I’ve been using STM32CubeIDE, STM32CubeMX, STM32CubeProgrammer, and STM32CubeMonitor on a Mac currently running macOS 26.6.

When I run env or export in Terminal (which uses Zsh by default), I find these two STM32-related environment variables.

STM32CubeMX_PATH=/Applications/STM32CubeMX.app/Contents/Resources
STM32_PRG_PATH=/Applications/STM32CubeProgrammer/STM32CubeProgrammer.app/Contents/Resources/bin

Examined Zsh dotfiles in my home folder and found the following two *export*s in ~/.zshrc that set them.

export STM32CubeMX_PATH=/Applications/STM32CubeMX.app/Contents/Resources
export STM32_PRG_PATH=/Applications/STM32CubeProgrammer/STM32CubeProgrammer.app/Contents/Resources/bin

Which apps have added these; CubeMX, CubeProg, or perhaps the respective plugins from CubeIDE? What is their intended purpose, and in particular, which other STM32Cube tools rely on them? Also, do the apps add these every time on launch or only once during installation?

[Mahmoud Ben Romdhane]

Hello ​@callsignhermit 

 

Let me thank you for posting.

The STM32CUBE*_PATH variables are added by the corresponding STM32Cube applications during installation, or at first launch when needed, so the tools can locate their resources from the shell environment.

In your case:

• STM32CubeMX_PATH is set by STM32CubeMX
• STM32_PRG_PATH is set by STM32CubeProgrammer

These variables are used internally by the applications and their launch scripts, especially on macOS/Linux, to ensure the tools can find their installed resources correctly. They are not typically added by STM32CubeIDE plugins.

They are generally created once during installation/configuration and should remain unchanged unless the application is reinstalled or moved to another location.

 

Thanks.

Mahmoud

[Alissia1240]

I have noticed the same environment variables on macOS and would also appreciate some clarification. It would be helpful to know which STM32Cube application creates STM32CubeMX_PATH and STM32_PRG_PATH—whether they are added by CubeMX, CubeProgrammer, STM32CubeIDE, or one of their plugins.

Could someone also explain their intended purpose and which STM32Cube tools depend on these variables? In addition, do the applications add these entries only once during installation, or are they recreated or updated whenever the applications are launched?

A clear explanation would help Mac users understand whether these variables are required, especially when managing or troubleshooting multiple STM32Cube tools.