Hey there !
Sorry to begin with a noob question. Have tried setting up a CrossPlatform compile on Ubuntu for Raspberry Pi dev. Following these links :
https:// github.com /plural/ofSite/commit/81672d808f3aa333c6b9c5fda365369792983b3e#diff-32f0a4873e229b5110cc199f4d4fedbeL29
Now moved to Unbutu 32bit and have exactly the same problem. Even re-did the pi setup…from installing ofx and running installdependencies to copying over the files from the pi to the 32bit Ubuntu install. Still can’t get this to work. Any help would be appreciated.
Still getting :src/tools/arm-unknown-linux-gnueabihf/bin/arm-unknown-linux-gnueabihf-g++: Command not found
Should the link look like this ?: src/tools/arm-bcm2708/arm-unknown-linux-gnueabihf/bin/arm-unknown-linux-gnueabihf-g++
arm-linux-gnueabihf-gcc -v returns the following :
Thanks for your reply Timoteus. I have run the ./fixQualifiedLibraryPaths script in the toolchain folder and in the original download folder, but with no luck on either 32bit or 64bit install.
Just ran it again and got this :Passed valid toolchain
Adjusting the symlinks in /home/USER/src/rootfs/usr/lib to be relative
Debian multiarch dir exists, adjusting
Adjusting the symlinks in /home/USER/src/rootfs/usr/lib/arm-linux-gnueabihf to be relative
USER@<USER-VirtualBox:~/Downloads/cross-compile-tools-cross-compile-tools$
I am using a 64 bit ubuntu install running on a virtual machine inside windows 7. When I first installed it I had similar problems. Some things that come to mind, there is no longer a ia32-libs package in ubuntu 14.04. I think I used sudo apt-get install libc6-i386 libz32z1 lib32stdc++6 instead.
This is exactly why I try to document as much as possible the development process in a separate google docs. Easy to pull solutions for these kinds of problems…
Also the linux history command is great
Let’s see, this is what I did according to the history command.
fresh ubuntu 14.04 install
download of 0.8.4 linux64 release
run install dependency
run install codecs
compile of
rsync -avu pi@192.168.1.8:/usr/ rpi-root/usr/
rsync -avu pi@192.168.1.8:/lib/ rpi-root/lib/
rsync -avu pi@192.168.1.8:/opt/ rpi-root/opt/
download rpi compiler and unzip to rpi-tools
download of 0.8.4 armv6 release
And my PATH variable is /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/tt/rpi-tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin
I added this in the end of the .bashrc file
PATH=$PATH:/home/tt/rpi-tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin
Hello Timoteus, thanks again for the reply. I think I have to give up on this I am afraid. My steps look to be similar to yours except for installing codecs. I have installed, complied and changed path variables, but still get, arm-unknown-linux-gnueabihf.
Hey again Timoteus, I was hoping to use OF for installation work. I haven’t gotten anywhere yet, but I was thinking that I could use it like an extension of Puredata with PI cams taking in real-time video and filtering the feeds/streams based on traffic patterns in the building/view of the camera.
I will also try another 64bit install later today.
yes!! guys, this arm-unknown issue, while can be solved by creating symlinks, can be done much simply if the /etc/debian file exists in your $RPI_ROOT (as documented in my other post).
Please let me know if anyone else can confirm my fixes are appropriate, as I’ve created the modified notes for the instructions site and can create a pull request to merge them into the official guide!
hi!
I am trying to follow the cross compiling guide and for me it is a bit unclear which install_dependencies.sh scripts needs to be executed and where they are located. Could someone shed some light onto the locations of these scripts both on the pi and on the linux system?
It should be this one for when doing it on the RPi:
openFrameworks/scripts/linux/debian_armv6l
and when you copy stuff over from the Pi to your host, you end up with the required tools and libraries. I did also run install_dependencies.sh (the ubuntu one) on the host previously, before setting up the cross compile in order for the native (ubuntu) builds to work, but I think this is probably not necessary if your sole purpose is to use the ubuntu system to do cross compiling.
What finally fixed this issue for me was placing the debian_version file at $RPI_ROOT/etc/debian_version. The guide makes it sound like it should be in root of $RPI_ROOT. Same goes for the /opt/vc directory. Don’t place vc in $RPI_ROOT, but in $RPI_ROOT/opt/.
