Reputation: 25
in my project, i using both Scons and Makefile to build. It working good when i use Makefile ,but got error when i use Scons
"arm-none-eabi-gcc -g -mthumb -mlittle-endian -mcpu=cortex-m4 -mcpu=cortex-m4 -Wl,--start-group -lm -lc -Wl,--end-group -Wl,--gc-sections -Wl,-Map,main.map -Tstm32_flash.ld -Wl,--entry=Reset_Handler -DSTM32F407xx -DUSE_STDPERIPH_DRIVER -I/home/minhtan/Downloads/STM32F4-Discovery_FW_V1.1.0/Utilities/STM32F4-Discovery -I/home/minhtan/Downloads/STM32F4-Discovery_FW_V1.1.0/Libraries/CMSIS/Include -I/home/minhtan/Downloads/STM32F4-Discovery_FW_V1.1.0/Libraries/CMSIS/ST/STM32F4xx/Include -I/home/minhtan/Downloads/STM32F4-Discovery_FW_V1.1.0/Libraries/STM32F4xx_StdPeriph_Driver/inc "-I/home/minhtan/Downloads/led(make file moi)" main.c -c -o main.o
sh: 1: arm-none-eabi-gcc: not found
scons: [main.o] Error 127
scons: building terminated because of errors. "
Upvotes: 2
Views: 4421
Reputation: 4052
This looks like the answer to #1 of our "most frequently asked" FAQs at http://scons.org/faq.html could help you out. By default, SCons doesn't import the variables like $PATH
from the surrounding shell environment. You have to pull in your $PATH
for properly detecting the arm-none-eabi-gcc
executable or specify the full path to the executable explicitly...check the mentioned FAQ entry for a more detailed discussion about why things are as they are, and how to provide the required $PATH
definitions to your build environments.
Upvotes: 1