Have I might had downloaded the crosscompiler wrong? Should I recompile all the libraries in my debian? They should be compatible if im using the very same compiler in Rpi and Debian, aren't they?Ĭould I continue compiling without the HF version? In that case, how can I overcome the problem with the OpenGL ES calls? What are the differences between the hf and non-hf versions? (I know hf is for hard floats, but without the hf it works with floats too) Then I modified my Makefile, so my CC= arm-linux-gnueabihf-gcc-4.6Īnd now, when I compile the simplest Hello World program, it gives me "Segmentation Fault" on execution.
MAKEFILE CROSS COMPILE C LINUX MAC OS INSTALL
So, I downloaded the gnueabihf compiler for my debian machine.Īpt-get install g++-4.6-arm-linux-gnueabihf
I supposed, the call fails could be caused by the different floating point conventions between GLES and my binaries. So I checked out the compiler in Rpi ("gcc -v") and shown up to be arm-linux-gnueabi hf-gcc. I supposed it to be related to the different compilations between my binary and the GLES libraries, cause im using the ones in the Rpi (and i supposed, that if they were built in arm architecture, the crosscompiler should be able to link them). The calls fail and the graphic mode is returned to text mode. The problem comes when I try to use any call to GL ES. With this, im able to compile programs in my machine and execute them from the Rpi. # xapt -a armel -m mesa-common-dev freeglut3 libgles2 # apt-get install g++-4.4-arm-linux-gnueabi # apt-get install emdebian-archive-keyring
MAKEFILE CROSS COMPILE C LINUX MAC OS WINDOWS
I have a windows machine with an vmware running a Debian 7.Ī set up the crosscompiler so i could compile in my Debian and execute on the Rpi.
Im new to cross compiling, and new to the Rpi, but im loving what i can see now.
0 kommentar(er)
