C'mon: If you're at ~/emmc
and then do a
sudo git clone https://github.com/Itseez/opencv.git
Then now opencv
is in
~/emmc/opencv
If you now do the following while still being in ~/emmc
sudo mkdir emmc/opencv/build
cd emmc/opencv/build
then opencv
is still in ~/emmc/opencv
but you created and changed into ~/emmc/emmc/opencv/build
while you wanted to be at ~/emmc/opencv/build
instead. There's is one step missing (cd ..
) or the occurences of emmc/
are too much.
I wrote exactly this two times already but it's obviously absolutely useless since you don't seem to take care of the difference between ~/emmc/emmc/opencv/build
(wrong) and ~/emmc/opencv/build
(right). The 'instructions' above simply can not work and that's just one of the mistakes. And it's always the same: As soon as @sinovoip posts instructions they're partially wrong so exactly nobody can benefit from. So why do you waste your time providing useless instructions again and again?
Same here: http://forum.banana-pi.org/t/bpi-m3-how-to-use-fatload-uenv-txt-script-bin-kernel-uimage/1245 Still wrong: scrip=script.bin
can NOT work! You've been told several times and you simply don't give a sh*t. There's still a t
missing. You not even fix such simple mistakes. And this pretty much describes the entirety of the catastrophic state of documentation and the lousy support situation.