-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Toolchain file update #233
Toolchain file update #233
Conversation
1. Use STM32_TOOLCHAIN_PATH if specified as environmental variable 2. Find tools like objcopy and size in default paths as well, which allows simply adding the binary folder of the toolchain to the path to find them. This also allows more consistent behaviour, because this already works for <cross-compile>-gcc/g++
Ok. Maybe we can merge it first? It looks finished, but I have not read everything yet |
I'm at work now. But looks fine, I will test ASAP and it can be merged regardless of other PR. As I said it was only for information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here setting STM32_TOOLCHAIN_PATH
in a env var, will make setting the value directly impossible. I think we want to check if the var is not set (using CLI or in the cmakelist) before using ENV var.
Co-authored-by: Julien Staub <[email protected]>
STM32_TOOLCHAIN_PATH
from environment if specified as environmental variablesimply adding the binary folder of the toolchain to the path to find them.
This also allows more consistent behaviour, because this already works
for -gcc/g++
closes #216