Launching SDK from the PlanAhead 14.4 or Vivado 2012.4 tools does not source the SDK environment properly.
From the PlanAhead or Vivado tool, I click File -> Export -> Export Hardware for SDK and check the "Launch SDK" checkbox.
SDK launches but is unable to find the ARM codesourcery toolchain.
The following error is issued when attempting to export and open a simple "hello world" sample project in SDK. the project will not compile and it looks like it cannot find the gnu compiler. Is this an environment variable issue?
**** Build of configuration Debug for project test1 ****
Building file: ../src/helloworld.c
Invoking: ARM gcc compiler
arm-xilinx-eabi-gcc -Wall -O0 -g3 -c -fmessage-length=0 -I../../test1_bsp/ps7_cortexa9_0/include -MMD -MP -MF"src/helloworld.d" -MT"src/helloworld.d" -o"src/helloworld.o" "../src/helloworld.c"
'arm-xilinx-eabi-gcc' is not recognized as an internal or external command,
operable program or batch file.
make: *** [src/helloworld.o] Error 1
This issue is due to the fact that the environment is not setup before SDK is invoked from the PlanAhead 14.4 or Vivado 2012.4 tool.
The environment SDK needs to function properly can be set by using the settings files generated by the installer.
When invoking PlanAhead and Vivado from program group/desktop shortcuts, the runtime environment is setup by the boot loaders and settings file are not used.
You can work around this problem by manually setting the SDK environment (e.g., run the settings32/64 .bat or .sh file).
In Vivado 2013.1 and PlanAhead 14.5 tool, this issue has been resolved by having the SDK boot loader construct an SDK runtime environment.
The Vivado boot loader will search the local install area ../../SDK/<same version as Vivado being used>. If SDK exists, set XILINX_SDK. If not, do not set it. No warnings, errors will be issued.