Forums » Software Development »
Eclipse CDT Builder problem when set up for cross compile
Added by Fred Weiser over 13 years ago
Hi.
I am getting the following error when attempting to build a project in Eclipse. I am not using CL's VM - my Eclipse version is 3.5.2 running on Ubuntu, and the cross compiler tool chain was installed per the CL wiki:
- Internal Builder is used for build **
arm-angstrom-linux-gnueabi-g++ -O0 -g3 -Wall -c -fmessage-length=0 -osrc/foo.o ../src/foo.cpp
Internal Builder: Cannot run program "arm-angstrom-linux-gnueabi-g++": Unknown reason
Build error occurred, build is stopped
Time consumed: 10 ms.
I have checked the toolchain installation by executing the same arm..g++ compiler command using a terminal - it works fine. I have also tried creating a new project, and it produces the same error. I also created a project that uses the native compiler and it works fine. Any ideas where I should look next? Do you know of a way to get more verbose output from CDT (internal builder)?
Thanks.
Replies (3)
RE: Eclipse CDT Builder problem when set up for cross compile - Added by Gregory Gluszek over 13 years ago
Hi Fred,
Where are you running the angstrom environment-setup script? We typically add this to the end of our bashrc and things work fine.
Also, how are you starting up Eclipse? Have you tried launching it from a terminal (where you've verified arm-angstrom-linux-gnueabi-g++ is working) and then compiling your project?
\Greg
RE: Eclipse CDT Builder problem when set up for cross compile - Added by Fred Weiser over 13 years ago
The angstrom environment-setup script is run at the end of my .bashrc file.
Running Eclipse from a shell known to "work" does indeed allow the cross compiler to run. When Eclipse is started using the Gnome launcher, it does not work... I guess I at least have a work-a-round for now.
:-/
RE: Eclipse CDT Builder problem when set up for cross compile - Added by Tim Iskander over 13 years ago
Fred,
There's a good chance that your bashrc file is no being read when you start it from the launcher. I don't remember the exact rules, but you may need to put the setup in your .bash_profile instead.
