How do I setup a kit to crosscompile for Raspbian for the Pi3?
-
Ok, so the paths are 100% the same? Does the compiler
arm-linux-gnueabihf-g++have the executable bit set? Sometimes you also have to call an "enviroment-setup" script to use the cross toolchain, not sure if that applies to your toolchain also.Btw:
arm-linux-gnueabihf-is the cross-toolchain-prefix, which tells you that the compiler produces "arm" executables for linux. "hf" stands for hardware floating point support and "gnueabi", I honestly would have to google it ;)g++is just the GNU GCC C++ compiler. Your normal compiler is therefore calledg++, and the cross-compiler is calledarm-linux-gnueabihf-g++.Double checked, yes it has the execution bit set for own, group and everyone else. I've added that bin to the path for good measure.
Here is something odd. If I cd into that bin directory and
./arm-linux-gnueabihf-g++the result
bash: ./arm-linux-gnueabihf-g++: No such file or directoryWhat seriously is wrong? The file is right in that directory! It even autocompletes for me! I really don't get this.
-
Double checked, yes it has the execution bit set for own, group and everyone else. I've added that bin to the path for good measure.
Here is something odd. If I cd into that bin directory and
./arm-linux-gnueabihf-g++the result
bash: ./arm-linux-gnueabihf-g++: No such file or directoryWhat seriously is wrong? The file is right in that directory! It even autocompletes for me! I really don't get this.
Puh, that's getting a tough one. But I don't give up yet. Can you please do a
file ./arm-linux-gnueabihf-g++in that directory and post the output here? -
Puh, that's getting a tough one. But I don't give up yet. Can you please do a
file ./arm-linux-gnueabihf-g++in that directory and post the output here?No problem:
./arm-linux-gnueabihf-g++: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.15, strippedok....is it a problem that that says intel and I'm running amd?
-
No problem:
./arm-linux-gnueabihf-g++: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.15, strippedok....is it a problem that that says intel and I'm running amd?
Ok, I think you your problem is, that this toolchain is for 32-Bit PC (i.e. x86), while you are probably running a 64 bit system (i.e. x86_64, you can check with the
archcommand).It might be possible to get this to run, but I'd rather recommend you to get a toolchain that directly runs on your system. you avoid the memory limits of 32 bit architecture with that also.
So far...
-
Ok, I think you your problem is, that this toolchain is for 32-Bit PC (i.e. x86), while you are probably running a 64 bit system (i.e. x86_64, you can check with the
archcommand).It might be possible to get this to run, but I'd rather recommend you to get a toolchain that directly runs on your system. you avoid the memory limits of 32 bit architecture with that also.
So far...
@aha_1980 Hmm...ok, maybe I missunderstood some of the instruction when it talked about 64bit. I assumed it was talking about the pi, which is 32bit, but yeah it's a brand new Ryzen machine, it's 64 bit.
I'll have to come back to this later today, but thank you for that. I'll let you know what I find.
-
Ok, I think you your problem is, that this toolchain is for 32-Bit PC (i.e. x86), while you are probably running a 64 bit system (i.e. x86_64, you can check with the
archcommand).It might be possible to get this to run, but I'd rather recommend you to get a toolchain that directly runs on your system. you avoid the memory limits of 32 bit architecture with that also.
So far...
-
Hmm...ok, maybe I missunderstood some of the instruction when it talked about 64bit. I assumed it was talking about the pi, which is 32bit
Don't worry, as said, cross compiling is advanced stuff ;)
arch command on my desktop:
x86_64Ok, that proves it.
-
arch command on my desktop:
x86_64If you're following the suggested RaspberryPi2EGLFS guide, in step #10 please pay attention to
If your system is 64 bit you may also edit device option to:
-
arch command on my desktop:
x86_64If you're following the suggested RaspberryPi2EGLFS guide, in step #10 please pay attention to
If your system is 64 bit you may also edit device option to:
Ok so I added the options for 64 bit, and looks like it all worked and compiled. So then I went to do the next step which is a test build, but there is no ~/raspi/qt5/bin/qmake
That directory doesn't exist, so now I really don't know what the hell to do. The previous steps created the qt5 and qt5pi folders so if there are missing directories, now what?
-
Ok so I got a lot farther using a different set of instructions, in fact I got to actually building in Qt Creator!!
However Qt Creator is failing to upload the file to the raspberry pi:
mkdir: cannot create directory ‘/opt/widgettest’: Permission denied 21:09:40: Failed to upload file "/home/brandon/development/build-widgettest-RaspPi-Release/widgettest". 21:09:40: Deploy step failed. Error while building/deploying project widgettest (kit: RaspPi) When executing step "Upload files via SFTP"How do I give Qt permission to do this? Do I need to dissable some security on the pi? Or add "sudo" to some commands in Qt?
-
You should either use credentials for your Pi that allows to write in that folder, or change the folder for something the user you use to connect to your RPi can write to.
-
You should either use credentials for your Pi that allows to write in that folder, or change the folder for something the user you use to connect to your RPi can write to.
-
even i am also getting same problem,I am very new this qt creator,I am using the ubuntu ,can you say step by step please..
@asha said in How do I setup a kit to crosscompile for Raspbian for the Pi3?:
can you say step by step please..
What have you done so far? Any errors you can share here?
Just in case, please refer to any of these guides:
