|TCF Agent [message #1770486]
||Sat, 12 August 2017 14:04
| Anne Creek
Registered: September 2014
Fri Aug 11, 2017 3:49 pm
This is my primary "how to " resource I am using to learn TCF.
I have been tru several similar tutorials , so I do not need another reference to "RTFM".
I am trying to understand how TCF works, not necessarily just "cut and paste"
I run into a dead end.
I have annotated the following steps
# (Replace n.n.n.n by the actual IP address that you read)
ssh firstname.lastname@example.org / password : raspberry
OK, I can communicate with RPi using ssh.
sudo apt-get update # (Need to update the Raspbian update caches to get git)
sudo apt-get install git uuid uuid-dev libssl-dev
git clone git://git.eclipse.org/gitroot/tcf/org.eclipse.tcf.agent.git
OK this clones lots of "agent " stuff - works fine so far
Move to created directory - works
cp R machine/arm machine/armv6l
Copy from /arm to NON-EXISTENT / armv61
I AM stuck here
1. WHY cp ?
2. What is "armv61", where did it come from?
I would really appreciate answer for the above so I can continue.
[Updated on: Sat, 12 August 2017 14:07]
Report message to a moderator
|Re: TCF Agent [message #1770492 is a reply to message #1770486]
||Sat, 12 August 2017 16:43
| Eugene Tarassov
Registered: July 2009
> 1. WHY cp ?|
> 2. What is "armv61", where did it come from?
By default, the agent makefile gets CPU architecture name by running `uname -m`, which returns armv6l on Raspberry Pi. The makefile uses the name to get architecture specific source files from machine/<arch> directory, then it creates a work directory obj/<OS name>/<arch>, e.g. obj/GNU/Linux/armv6l.
However, we don't have machine/armv6l subdirectory. Instead we have single subdirectory for all 32-bit ARM variants. So, you can either use cp to create armv6l , or, an easier way is to use MACHINE=arm to override the architecture name and use generic arm directory:
Powered by FUDForum
. Page generated in 0.01427 seconds