树莓派-交叉编译环境搭建(Eclipse)

小灰灰 2021-12-13 14:39 589阅读 0赞

转自别人的文章（[http://www.cnblogs.com/emouse/archive/2013/06/07/3124063.html][http_www.cnblogs.com_emouse_archive_2013_06_07_3124063.html]），一些看不清楚的图片替换了一下。

In this blog  entry the setup of  a cross-compiling development environment for the Raspberry Pi will be demonstrated. This will include the

*  [Official Raspbian (armhf) cross compiling toolchain ][Official Raspbian _armhf_ cross compiling toolchain](available from github)
 *  [Eclipse for C/C++ Developers (Linux 32-bit)][Eclipse for C_C_ Developers _Linux 32-bit]

We will finally write a simple Hello World program on our Kubuntu virtual machine (VM), compile it using the cross compiler and then deploy it onto our Raspberry Pi board to run it.

I’m going to assume that you have already[ installed a Raspbian Wheezy image on your RPi board ][installed a Raspbian Wheezy image on your RPi board]and that you have Ubuntu / Kubuntu Linux installed either has a host OS or [guest OS][] on your desktop PC.

A remote debugging tutorial; which I consider to be the continuation of this tutorial, can be found [here][].

**So what is a cross compiling toolchain and why use one ?    **

A native compiler such as the default gcc tool on Kubuntu  is a compiler that runs on an Intel machine, as well as creates binaries intended to be run on an Intel machine. i.e it creates binaries for the same type of machine that it runs on. Similarly the GCC tool in the RPi’s Raspbian Linux OS is intended to run on an ARM machine as well as creates binaries for an ARM machine.

A cross compiler such as the “arm-linux-gnueabihf-gcc” that we will use is able to run on an Intel machine but creates binaries for an ARM machine. In other words, it runs on one architecture and creates binaries for another. This allows us to develop and compile our programs on our Desktop PC but when it comes to deploying the binaries we deploy them and run them on the Raspberry Pi.

So why use a Cross-compiler instead of  developing our code and compiling it natively on the Raspberry Pi itself? After all, the Raspberry Pi has a native GCC compiler. We can also use code editors such as nano or vi from the command line (remotely over SSH) or GUI programs such as Geany (remotely over VNC).

The main case for cross-compilation over native compilation (develop and compile on the RPi itself) is that it tends to be faster. Remember the RPi board may be fast compared to a microcontroller…but its still has limited RAM resources and is pretty slow compared to an average desktop computer….

Also you have a myriad of development tools that you can use on your desktop PC that you simply can’t use on the Raspberry Pi; such as the Eclipse IDE.

Now that I’ve explained the why…let’s get started!

**Downloading and Setting Up the Cross Compiling Toolchain**

*  Open a terminal window on your desktop side Kubuntu/Ubuntu Linux OS and type the following command: “**sudo apt-get install git**“. This will install the GIT tool on your desktop linux box which in turn will enable us to download / clone the cross compiling toolchain from GitHub.com.
 *  If you’re running a 64-bit Ubuntu/Kubuntu Linux OS you will probably also want to install the 32-bit library/header files. Since the cross compiler will need them to properly run. You can do this by typing “**sudo apt-get install ia32-libs**“. Again this step is only required if you are running a 64-bit Linux OS.
 *  Once git is installed, create a “raspberrypi” directory in your home directory by typing “**mkdir raspberrypi**“.
 *  Go to the raspberrypi directory by “**cd raspberrypi”** and then type:** “sudo git clone git://github.com/raspberrypi/tools.git**“
 *  This command will download (clone) Raspbian’s official cross compiling toolchain from Github. The command will take a few minutes to complete its task.
 *  When the previous command completes, navigate to “/home/halherta/raspberrypi/tools/arm-bcm2708″ using “**cd ~/raspberrypi/tools/arm-bcm2708**” on your Deskop Linux OS.
 *  In the arm-bcm2708 folder you’ll see three other folders each containing a separate toolchain:

1.  arm-bcm2708-linux-gnueabi
2.  arm-bcm2708hardfp-linux-gnueabi
3.  gcc-linaro-arm-linux-gnueabihf-raspbian

Of those three we will use the third one. The next step is to add the directory containing the binary files of the third toolchain “gcc-linaro-arm-linux-gnueabihf-raspbian” to the PATH environment variable in linux. This way we can access the toolchain’s binary files from anywhere on our computer. We will do this by adding an “export PATH”  command to the bottom of the .bashrc and .profile files in the home directory.

*  In a terminal window (on your Desktop Linux OS) type “**cd ~/**“  to point to the home directory, then type “**nano .bashrc**“. This will open the .bashrc file in a command line based editor called nano. Go to the bottom of the .bashrc file using the down arrow key. Then type the following command:

**“export PATH=$PATH:$HOME/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin”**

*  Then hit Ctrl+x to exit. You will be prompted to save changes. Say yes and hit “Enter”.

*  Similarly in our home directory type “**nano .profile**“. This will open the .profile file in the command line editor nano. Go to the bottom of the .profile file using the down arrow key. Then type the same command again:

**“export PATH=$PATH:$HOME/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin”**

*  Then hit Ctrl+x to exit. You will be prompted to save changes. Say yes and hit “Enter”.

Now restart your machine. (You probably could just log out and log in again)

Ideally you need to export the toolchain’s directory path to the PATH variable in either the .bashrc or the .profile files. This didn’t work for me. If it works for you thats great.

When you log-in  into your desktop Linux OS, open a new console window and type: ” arm-linux-gnueabihf-gcc -v”. If you were successful you should see output similar to that in Figure 1. Congratulations! you just installed Raspbian’s official cross compiling toolchain on your Desktop PC / Virtual Machine!

[![Image(3)][Image_3]][Image_3_Image_3]

Figure 1. Cross Compiling Toolchain successfully installed and accessible from anywhere within your Desktop side Linux OS!!!

**Downloading and Setting Up Eclipse**

The Next step is to download and install Eclipse. Unfortunately as of this writing the apt-get repositories have yet to contain the latest Eclipse build…Eclipse Juno. So we will not be using the apt-get package manager. Instead we will download the latest Eclipse IDE from the web using a web browser.

*  Before we can run eclipse, we need to ensure that we have a Java runtime environment installed; since eclipse relies heavily on Java. We can do this with the following command: “**sudo apt-get install openjdk-7-jre**“
 *  Go to the link provided below and download the linux version of the Eclipse IDE (Juno) for C/C++. Download the 32-bit version of the IDE if you’re running a 32-bit Linux OS or download the 64-bit version of the IDE if you’re running a 64-bit Linux OS.

Link: [http://www.eclipse.org/downloads/packages/eclipse-ide-cc-developers/junor][Eclipse for C_C_ Developers _Linux 32-bit]

*  If you’re not sure whether you’re running a 64-bit or 32-bit Linux OS, open a terminal window and type” **uname -a**“. If  the output of that command contains “i686″ or “i386″, you’re running a 32-bit Linux OS. If in the output you see “x64″ then you’re running a 64-bit Linux OS.
 *  The next step is to extract the “eclipse” folder into our home directory from the eclipse-cpp-juno-linux-gtk.tar.gz compressed file. This can be easily done using the Dolphin File Manager. Navigate to the directory in which “eclipse-cpp-juno-linux-gtk.tar.gz” was downloaded. Click on the file. This will open a decompression tool. Click on extract and choose to extract to the /home/halherta directory. Alternatively open a new console and navigate to the directory containing the .gz file then type: “**tar -xvzf eclipse-cpp-juno-linux-gtk.tar.gz -C ~/**“. Either way you will end up having  the eclipse directory created in your home directory. To start eclipse, go to the home directory “**cd ~/**” then ‘cd’ your way into the eclipse folder “**cd eclipse**” then type “**./eclipse &**“.
 *  If you have been following my series of tutorials from scratch and/or are running Kubuntu, you can enable starting eclipse from the start menu right click on the blue KDE start menu button and click on  “Edit Applications”. This will open the KDE Menu Editor.
 *  Select on the “Development” tab in the right of the window and then click on the “new item” button. A message box will pop-up. Enter under “item name”: “Eclipse Juno for C/C++ Developers”. Then click on the “open file dialog” adjacent to the “command field” and select the eclipse binary which should be “/home/halherta/eclipse/eclipse”. Furthermore, click on the icon box. This will open an icon source box select the “other icon” option  and then click on the browse button. Browse to the “/home/halherta/eclipse/” folder and then select the “icon.xpm” file.

[![Image(4)][Image_4]][Image_4_Image_4]

Figure 2. Choose “Other Icons” and hit “Browse” button to select “icon.xpm” file in the eclipse directory

*  After these changes the KDE Menu Editor window should look like the illustration shown in Figure 3.

Figure 2. Choose “Other Icons” and hit “Browse” button to select “icon.xpm” file in the eclipse directory

*  Finally click on the “Save” button and then close the KDE Menu Editor. If you now navigate the KDE  menu, you should find eclipse under “Applications->Development”. If you click on it the Eclipse IDE should start.
 *  Note if you’re running Ubuntu (without Unity…just gnome classic) you can right click on the “Applications Menu” and select “Edit Menu” to edit your gnome-based Ubuntu start menu and add to it an entry for eclipse in a similar manner as demonstrated above. And don’t ask me about Ubuntu Unity integration..I hate it.

**Creating a New Project in Eclipse**

When Eclipse runs, it will first launch the workspace launcher. You will be prompted to choose a workspace directory. Accept the default. Feel free to check the “Use this as the default and do not ask again” option if you feel inclined to do so. (You can always switch/change the workspace directory by going to “File->Switch Workspace” ).

[![Image(5)][Image_5]][Image_5_Image_5]

Figure 4. Workspace launcher

*  You should then see a Welcome Tab (Figure 5). Click on the ‘x’ on the Welcome tab to close it

[![Image(6)][Image_6]][Image_6_Image_6]

Figure 5. Welcome Tab. Click on the ‘x’ in the tab to close it

*  Now go to File->New->C++ Project. This will open the “C++ Project” window shown in Figure 6.

[![Image(7)][Image_7]][Image_7_Image_7]

Figure 6. C++ Project Window

*  Type “HelloWorld” in the “Project Name” field. Under Project type select “Executable->Empty Project” Under “Toolchains” select “Linux GCC”. Then click on “Next” This should take you to the “Select Configurations” Window. Accept the defaults and click “Finish”.

*  This should be the end of the basic project configuration. Your Eclipse Environment should look as shown in Figure 7.

[![Image(8)][Image_8]][Image_8_Image_8]

Figure 7. New Hello World Project initial setup

*  Notice how this project does not have any source files so lets add one. Click on “File->New Source File”. This should open the “New Source File” window.

[![Image(9)][Image_9]][Image_9_Image_9]

Figure 8. New source File Window.

*  Ensure that the “Source folder” and “Source file” fields include “HelloWorld” and “HelloWorld.cpp” respectively as shown in Figure 8 and click Finish. This will add a HelloWorld.cpp source file to our project. In the source file type the following basic C++ code:

*  ![复制代码][copycode.gif]
    
    ![复制代码][copycode.gif]
    
        /*
         * HellWorld.cpp
         *
         *  Created on: 2012-09-27
         *      Author: halherta
         */
         
        #include <iostream>
         
        using namespace std;
         
        int main (void)
        {
            cout << "Hello RPi Development World !"<< endl;
            return 0;
         
        }
    
    ![复制代码][copycode.gif]
    
    ![复制代码][copycode.gif]
    
    Save your project by clicking on “File->Save”.
 *  Now we will need to access the Project properties to ensure that the correct compiler (the Raspbian cross compiler)  and its header and library files are being used. To do this select the “HelloWorld” folder/project in the project explorer and then click on project properties. This will open the “Properties for HelloWorld” window.

[![Image(10)][Image_10]][Image_10_Image_10]

![251620155316536.png][]

Figure 9.

*  First go to “C/C++ General -> Paths and Symbols” from the left hand side navigation bar. In the “Includes” Tab make sure that all the include paths included in Figure 9 are added.

Then go to the “Library Paths” and make sure that all the library paths in Figure 10 are added.

[![Image(11)][Image_11]][Image_11_Image_11]

![251620437346186.png][]

Figure 10. Library Path for the Cross Compiler

*  Finally go to “C/C++ Build -> Settings” (Figure 11) from the left hand side navigation bar. Under the “Tool Settings” Tab select “GCC C++ Compiler” for that Tab’s Navigation bar and ensure that the command field contains: “arm-linux-gnueabihf-g++”
 *  Similarly the command field for the “GCC C Compiler” should contain “arm-linux-gnueabihf-gcc”
 *  Similarly the command field for the “GCC C++ Linker” should contain “arm-linux-gnueabihf-g++”
 *  And finally the command field for the “GCC Assembler” should contain “arm-linux-gnueabihf-as.

[![Image(12)][Image_12]][Image_12_Image_12]

Figure 11. C/C++ Build->Settings

Then click on the Apply and OK buttons. At this point the Eclipse IDE is configured to utilize the Raspbian cross compiler.

To build the project click on “Project->Build Project”. To clean the project click on “Project->Clean”. Figure 12 shows the Eclipse workspace with the HelloWorld program successfully cross compiled for the Raspberry Pi!!!

[![Image(13)][Image_13]][Image_13_Image_13]

Figure 12. HelloWorld program successfully compiled for Raspberry Pi.!!!

The binary file for our HelloWorld application resides in  the “~/workspace/HelloWorld/Debug”. Lets go there via a console window with cd “**cd ~/workspace/HelloWorld/Debug/**“. If we  type in “**ls -al**” we’ll find that our Binary file is highlighted in green and is called HelloWorld. If I try to run it with “**./HelloWorld**” I get the following error message “**cannot execute binary file**“. Now if I type “**file HelloWorld**“, I get the following output: “**HelloWorld: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.26, BuildID\[sha1\]=0xb37e6eaa466429d015cc334d55f5d46c97c9fc6c, not stripped**“. This indicates that the HelloWorld Binary File was compiled for a 32-bit ARM machine and cannot run on an Intel Machine.

**Deploying the Binary file onto the Raspberry Pi**

To deploy the binary to the Raspberry Pi, make sure that the RPi board is powered and connected to your network. The next step is click on “Window->Show View->Other”. This will open a show view window. In this window select the “Remote Systems” folder and then select “Remote Systems Details” and press OK (Figure 13).

[![Image(14)][Image_14]][Image_14_Image_14]

Figure 13. Remote system view

*  If the “Remote Systems Details” shows up in the bottom of the workspace, drag it such that its tab shares  the same region as the project explorer tab as shown in Figure 14.

[![Image(15)][Image_15]][Image_15_Image_15]

Figure 14.

*  Now right click in the “Remote Systems Detail” area and click on “New Connection”. In the “Select Remote System Type” window (Figure 15), select “SSH only” then click “Next”

[![Image(16)][Image_16]][Image_16_Image_16]

Figure 15.

*  In the “Remote SSH Only System Connection” type in the IP address of the RPi in the “Host name” field and give the connection a valid name in the “Connection name” field. I typed “RaspberryPi”.  Then click “Finish”.

[![Image(17)][Image_17]][Image_17_Image_17]

Figure 16.

*  At this point a second device (Raspberry Pi) shows up in the “Remote Systems Detail” tab. Right click on the Raspberry Pi resource and click connect. You will be prompted to enter the username and password. Make sure that you utilize “username:pi” and “password:raspberry” (if you haven’t changed the default password). You may get a warning windows asking you if you are sure that you want to accept this connection. Affirm that you want to proceed with the connection. At this point you should be connected to your RPi from eclipse

[![Image(18)][Image_18]][Image_18_Image_18]

Figure 17.

*  Right click on the Raspberry Pi resource again  in the “Remote Systems Detail” tab and click on the “Show in Remote Systems View”. This will open a “Remote Systems” tab in the same region of the workspace. In this tab, one can navigate the root file systems of both the Kubuntu (local) OS and that of the Raspbian/Raspberry Pi.
 *  Locate the HelloWorld Binary file on our local desktop PC and drag it to the home directory on the Raspberry Pi. This effectively copies the Binary file to the home directory of the Raspberry Pi.

[![Image(19)][Image_19]][Image_19_Image_19]

Figure 18.

*  Now right click on the SSH terminal icon under the Raspberry Pi icon in the  “Remote Systems” and select “Launch Terminal” . This should launch a terminal window in the bottom of the Eclipse workspace (Figure 19). This is basically a console / terminal window connected to the Raspberry Pi via SSH.

[![Image(20)][Image_20]][Image_20_Image_20]

Figure 19.

*  In the terminal window type “**ls -al**” to confirm that the “HelloWorld” binary indeed got copied into the home directory of the Raspberry Pi’s root file system. Then change the “HelloWorld” binary’s permission to make it executable: “**chmod +x HelloWorld**“
 *  Finally type “**./HelloWorld**“. You should see the output shown in Figure 19. :**“Hello RPi Development World !”**
 *  Congratulations!!! You just developed and ran your first cross compiled application for the Raspberry Pi.!!!!
 *  To remotely debug your applications on the Raspberry Pi from Eclipse, check out [this blog entry!][here]

[http_www.cnblogs.com_emouse_archive_2013_06_07_3124063.html]: http://www.cnblogs.com/emouse/archive/2013/06/07/3124063.html
[Official Raspbian _armhf_ cross compiling toolchain]: https://github.com/raspberrypi/tools
[Eclipse for C_C_ Developers _Linux 32-bit]: http://www.eclipse.org/downloads/packages/eclipse-ide-cc-developers/junor
[installed a Raspbian Wheezy image on your RPi board]: http://hertaville.com/2012/09/27/raspbian-raspberry-pi/
[guest OS]: http://hertaville.com/2012/09/27/kubuntu-vmware-player/
[here]: http://hertaville.com/2013/01/11/remote-debugging/
[Image_3]: https://images0.cnblogs.com/blog/337520/201306/07161618-d92c35a4b8a5419f9d0e31999a085f94.png
[Image_3_Image_3]: http://hertaville.com/wp-content/uploads/2012/11/cc110.png
[Image_4]: https://images0.cnblogs.com/blog/337520/201306/07161620-665d24ec13bd41a08a1c72789fe7f480.png
[Image_4_Image_4]: http://hertaville.com/wp-content/uploads/2012/11/cc21.png
[Image_5]: https://images0.cnblogs.com/blog/337520/201306/07161625-b89cfadd53e2442c8a6c0215a746e825.png
[Image_5_Image_5]: http://hertaville.com/wp-content/uploads/2012/11/cc41.png
[Image_6]: https://images0.cnblogs.com/blog/337520/201306/07161626-9beac2eeb33f4aa88df7e41847765528.png
[Image_6_Image_6]: http://hertaville.com/wp-content/uploads/2012/11/cc51.png
[Image_7]: https://images0.cnblogs.com/blog/337520/201306/07161627-fee3f76351044572aced39c322515c46.png
[Image_7_Image_7]: http://hertaville.com/wp-content/uploads/2012/11/cc62.png
[Image_8]: https://images0.cnblogs.com/blog/337520/201306/07161627-f03167f5b99843a6a0b2b6c7b255f1cf.png
[Image_8_Image_8]: http://hertaville.com/wp-content/uploads/2012/11/cc71.png
[Image_9]: https://images0.cnblogs.com/blog/337520/201306/07161628-34edfcb57cb24be1bd1556ebeb42256c.png
[Image_9_Image_9]: http://hertaville.com/wp-content/uploads/2012/11/cc82.png
[copycode.gif]: /images/20211213/5f819c94c6b54dfe811be058a49b336b.png
[Image_10]: https://images0.cnblogs.com/blog/337520/201306/07161654-4fbd6f74824d4f56ba9b4d3ebaa60103.png
[Image_10_Image_10]: http://hertaville.com/wp-content/uploads/2012/11/cc91.png
[251620155316536.png]: /images/20211213/fa5ede81a064441f8afb4d147e32b946.png
[Image_11]: https://images0.cnblogs.com/blog/337520/201306/07161708-192ba6df0c364de19c4565944c989aa8.png
[Image_11_Image_11]: http://hertaville.com/wp-content/uploads/2012/11/cc101.png
[251620437346186.png]: /images/20211213/e83f28e6a8ab4c9a83297510f6822ffd.png
[Image_12]: https://images0.cnblogs.com/blog/337520/201306/07161709-b1c0a159101a4d1192640d8e9fc0ea51.png
[Image_12_Image_12]: http://hertaville.com/wp-content/uploads/2012/11/cc8.11.png
[Image_13]: https://images0.cnblogs.com/blog/337520/201306/07161711-9b10f0bb526f4bfcad9575922946b46a.png
[Image_13_Image_13]: http://hertaville.com/wp-content/uploads/2012/11/cc111.png
[Image_14]: https://images0.cnblogs.com/blog/337520/201306/07161712-8f59e6b98cce4608a477eb8461acffb0.png
[Image_14_Image_14]: http://hertaville.com/wp-content/uploads/2012/11/cc121.png
[Image_15]: https://images0.cnblogs.com/blog/337520/201306/07161714-599e1c5382be47e0abf786d3e21154f8.png
[Image_15_Image_15]: http://hertaville.com/wp-content/uploads/2012/11/cc131.png
[Image_16]: https://images0.cnblogs.com/blog/337520/201306/07161736-5b197a0d8dc648c6a9739eaa2cdf94ea.png
[Image_16_Image_16]: http://hertaville.com/wp-content/uploads/2012/11/cc141.png
[Image_17]: https://images0.cnblogs.com/blog/337520/201306/07161758-41f3f65a4aee40ec95353d70912ddcf4.png
[Image_17_Image_17]: http://hertaville.com/wp-content/uploads/2012/11/cc151.png
[Image_18]: https://images0.cnblogs.com/blog/337520/201306/07161801-bad603c1bd064b8e9ab88f9426324b10.png
[Image_18_Image_18]: http://hertaville.com/wp-content/uploads/2012/11/cc171.png
[Image_19]: https://images0.cnblogs.com/blog/337520/201306/07161804-0570a117d2ee4d5c806e3ebbbaec837a.png
[Image_19_Image_19]: http://hertaville.com/wp-content/uploads/2012/11/cc181.png
[Image_20]: https://images0.cnblogs.com/blog/337520/201306/07161806-05c2f8282c0c4d469b6f18294142ae01.png
[Image_20_Image_20]: http://hertaville.com/wp-content/uploads/2012/11/cc191.png