| GCC Cross compiler configuration [message #1770186] |
Tue, 08 August 2017 23:00  |
 Anne Creek
Messages: 275
Registered: September 2014 |
Senior Member |
|
|
In the Cross compiler prefix text box, enter arm-none-eabi-, including the hyphen (-) at the end, to specify the correct compiler for Armstrap targets.
In the Cross compiler path text box, browse to the location of the <user>/Desktop/armstrap/gcc-arm/bin directory to specify the location of the compiler.
OK , building cross compiled project , thus selecting GCC cross
Now I need to configure Cross compiler prefix and Cross compiler path.
I COULD just "cut and paste " from the above example, but I like to know why.
How are these entries made , what resources are needed.
For example where do I get the (embedded hardware ) target name from BEFORE I start building my
new project.
Is "make target" same as cross compiler target?
Probably not because it can be "made" after the project is build.
Update
OK , found this under in /usr/bin on the target hardware
arm-linux-gnueabihf-gcc-4.9
is that "GCC prefix " ?
Question
If I want to continue discussion should I edit the OP or add to it?
OK, I got few @problems@ configuring cross GCC
When I add JUST the above prefix and press a button the Eclipse "takes off" and I loose control of configuration.
If I just press "browse" to look for the location of GCC on the host (RPI) I get to choose from "This computer". That tells me that I need to have some path directing me to the host already. There are samples of code for Windows , but nothing to tell me how to set the path to the host in Linux.
Perhaps something like this <user>/Desktop/armstrap/gcc-arm/bin ?
Apparently incorrect GCC path triggers @New Connection@ which it really confusing at this point since I do not have "Targer" specified , not yet.
[Updated on: Wed, 09 August 2017 13:59] Report message to a moderator |
|
|
|
|
|
|
| Re: GCC Cross compiler configuration [message #1770317 is a reply to message #1770269] |
Wed, 09 August 2017 22:31  |
Anne Creek
Messages: 275
Registered: September 2014 |
Senior Member |
|
|
So I need to identify the entire path to my (cross) compiler on the host , where my finished executable will be,
and it is not /usr/bin/gcc ?
Am I looking for "arm " GCC ? My host is ARM architecture.
Apparently this package is missing from my OS
whereis gcc-arm-none-eabi
but my prefix is correct arm-linux-gnueabihf-gcc-4.9
I think I can figure it now, thanks.
[Updated on: Wed, 09 August 2017 22:52] Report message to a moderator |
|
|
|
|
|
| Re: GCC Cross compiler configuration [message #1770398 is a reply to message #1770352] |
Thu, 10 August 2017 17:09 |
Anne Creek
Messages: 275
Registered: September 2014 |
Senior Member |
|
|
Tauno Voipio wrote on Thu, 10 August 2017 09:57Vaclav Sal wrote on Thu, 10 August 2017 01:31 So I need to identify the entire path to my (cross) compiler on the host , where my finished executable will be,
and it is not /usr/bin/gcc ?
Am I looking for "arm " GCC ? My host is ARM architecture.
Apparently this package is missing from my OS
whereis gcc-arm-none-eabi
but my prefix is correct arm-linux-gnueabihf-gcc-4.9
I think I can figure it now, thanks.
You seem to mix up the compilers generating code for the computer it is run on (usually called 'host').
You *do* need an 'arm-linux-gnueabihf-' toolset on your host computer for Pi. Please note that there is more than just gcc in the toolset:
- gcc (with cc1 and cpp)
- as
- ld
- other binary uitlities
- runtime libraries
- linker scripts for target
arm-none-eabi- toolset is targeted for raw hardware, mostly small embedded chips. It is not the right one for Raspberry Pi.
Please read the references I showed in previous post.
Yes, I am pretty mixed up - it is a long and crooked way from "cross GCC"
to ARM compiler (toolset) build for specific hardware.
The terminology is not always intuitive - in SSH I have server and client , in "cross compiling " I have a "host".
So what do you call the machine where I am using Eclipse to write the software on ?
Anyway, I did some research before posting here and still not sure how "prefix" gets to be AFTER the path entry.
Should prefix be in FRONT?
I sure appreciate all the help I am getting here, you guys are awesome.
Thanks
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05641 seconds
] 
Search
Help
Register
Login
Home
