From d5ae7d902a40f26a8c26f4c6d300226689738716 Mon Sep 17 00:00:00 2001 From: Brad Bishop Date: Thu, 14 Jun 2018 09:52:03 -0700 Subject: Sumo refresh Update external subtrees to latest Yocto sumo. Change-Id: I8364f32bef079841c6e57f1c587f4b1bedf62fef Signed-off-by: Brad Bishop --- .../documentation/sdk-manual/sdk-appendix-neon.xml | 297 ++++++++++++--------- 1 file changed, 174 insertions(+), 123 deletions(-) (limited to 'poky/documentation/sdk-manual/sdk-appendix-neon.xml') diff --git a/poky/documentation/sdk-manual/sdk-appendix-neon.xml b/poky/documentation/sdk-manual/sdk-appendix-neon.xml index f648047ef..0fb92985a 100644 --- a/poky/documentation/sdk-manual/sdk-appendix-neon.xml +++ b/poky/documentation/sdk-manual/sdk-appendix-neon.xml @@ -14,8 +14,8 @@ from start to finish. For general information on using the Eclipse IDE and the Yocto Project Eclipse Plug-In, see the - "Developing Applications Using Eclipse" - Chapter. + "Application Development Workflow Using Eclipse" + section.
@@ -53,13 +53,18 @@ http://www.eclipse.org/neon/. Download the Tarball: - Click the "Download" button and then use the "Eclipse - IDE for C/C++ Developers" - appropriate for your development system. + Click the "Download" button and look for the + "Eclipse IDE for C/C++ Developers" Neon 3 Package. + Select the correct platform download link listed at + the right. + For example, click on "64-bit" next to Linux if your + build host is running a 64-bit Linux distribution. + Click through the process to save the file. Unpack the Tarball: - Move to a clean directory and unpack the tarball. - Here is an example: + Move to a directory and unpack the tarball. + The following commands unpack the tarball into the + home directory: $ cd ~ $ tar -xzvf ~/Downloads/eclipse-cpp-neon-3-linux-gtk-x86_64.tar.gz @@ -84,11 +89,22 @@ Follow these steps to configure the Neon Eclipse IDE. - - Depending on how you installed Eclipse and what you have - already done, some of the options will not appear. - If you cannot find an option as directed by the manual, - it has already been installed. + Notes + + + Depending on how you installed Eclipse and what + you have already done, some of the options do + not appear. + If you cannot find an option as directed by the + manual, it has already been installed. + + + If you want to see all options regardless of + whether they are installed or not, deselect the + "Hide items that are already installed" + check box. + + Be sure Eclipse is running and @@ -164,11 +180,11 @@ in the URL field and provide a meaningful name in the "Name" field. - Click "OK" to have the entry added - to the "Work with:" drop-down list. - - Select the entry for the plug-in - from the "Work with:" drop-down list. + + Click "OK" to have the entry automatically + populate the "Work with:" field and to have + the items for installation appear in the window + below. Check the boxes next to the following: @@ -196,8 +212,14 @@ To install the Neon Eclipse Yocto Plug-in from the latest source code, follow these steps: - Be sure your development system - has JDK 1.8+ + + Be sure your build host has JDK version 1.8 + or greater. + On a Linux build host you can determine the + version using the following command: + + $ java -version + install X11-related packages: @@ -211,18 +233,19 @@ $ git clone git://git.yoctoproject.org/eclipse-yocto - Use Git to checkout the correct - tag: + + Use Git to create the correct tag: $ cd ~/eclipse-yocto - $ git checkout neon/yocto-&DISTRO; + $ git checkout -b neon/&DISTRO_NAME_NO_CAP; remotes/origin/neon/&DISTRO_NAME_NO_CAP; This creates a local tag named - neon/yocto-&DISTRO; based on - the branch origin/neon-master. - This puts you in a detached HEAD state, which - is fine since you are only going to be building - and not developing. + neon/&DISTRO_NAME_NO_CAP; + based on the branch + origin/neon/&DISTRO_NAME_NO_CAP;. + You are put into a detached HEAD state, + which is fine since you are only going to + be building and not developing. Change to the scripts @@ -243,20 +266,22 @@ directory of the Git repository created earlier. - Run the build.sh + + Run the build.sh script as directed. - Be sure to provide the tag name, documentation - branch, and a release name. - - Following is an example: + Be sure to provide the tag name, + documentation branch, and a release name. + + Following is an example: - $ ECLIPSE_HOME=/home/scottrif/eclipse-yocto/scripts/eclipse ./build.sh -l neon/yocto-&DISTRO; master yocto-&DISTRO; 2>&1 | tee build.log + $ ECLIPSE_HOME=/home/scottrif/eclipse-yocto/scripts/eclipse ./build.sh -l neon/&DISTRO_NAME_NO_CAP; master yocto-&DISTRO; 2>&1 | tee build.log - The previous example command adds the tag you - need for neon/yocto-&DISTRO; - to HEAD, then tells the - build script to use the local (-l) Git checkout - for the build. + The previous example command adds the tag + you need for + neon/&DISTRO_NAME_NO_CAP; + to HEAD, then tells + the build script to use the local (-l) Git + checkout for the build. After running the script, the file org.yocto.sdk-release-date-archive.zip is in the current directory. @@ -310,7 +335,7 @@
- Configuring the Neon Eclipse Yocto Plug-in + Configuring the Neon Eclipse Yocto Plug-In Configuring the Neon Eclipse Yocto Plug-in involves setting the @@ -324,14 +349,16 @@ To start, you need to do the following from within the Eclipse IDE: - - Choose "Preferences" from the + + + Choose "Preferences" from the "Window" menu to display the Preferences Dialog. - Click "Yocto Project SDK" to display + + Click "Yocto Project SDK" to display the configuration screen. - + The following sub-sections describe how to configure the the plug-in. @@ -354,15 +381,15 @@ the sysroot location, and select the target architecture. - Selecting the Toolchain Type: - Choose between - Standalone pre-built toolchain + + Selecting the Toolchain Type: + Choose between "Standalone pre-built toolchain" and - Build system derived toolchain - for Cross Compiler Options. + "Build system derived toolchain" for Cross Compiler + Options. - - Standalone Pre-built Toolchain: + + Standalone Pre-built Toolchain: Select this type when you are using a stand-alone cross-toolchain. For example, suppose you are an @@ -376,24 +403,25 @@ and installed a pre-built toolchain for an existing image. - - Build System Derived Toolchain: + + Build System Derived Toolchain: Select this type if you built the toolchain as part of the Build Directory. - When you select - Build system derived toolchain, - you are using the toolchain built and - bundled inside the Build Directory. + When you select "Build system derived + toolchain", you are using the toolchain + built and bundled inside the Build + Directory. For example, suppose you created a suitable image using the steps in the wiki. - In this situation, you would select the - Build system derived toolchain. + In this situation, you would select + "Build system derived toolchain". - Specify the Toolchain Root Location: + + Specify the Toolchain Root Location: If you are using a stand-alone pre-built toolchain, you should be pointing to where it is installed (e.g. @@ -402,10 +430,10 @@ "Installing the SDK" section for information about how the SDK is installed. + If you are using a build system derived toolchain, the path you provide for the - Toolchain Root Location - field is the + "Toolchain Root Location" field is the Build Directory from which you run the bitbake command (e.g @@ -414,10 +442,12 @@ "Building an SDK Installer" section. - Specify Sysroot Location: + + Specify Sysroot Location: This location is where the root filesystem for the target hardware resides. + This location depends on where you separately extracted and installed the target filesystem when you either built @@ -438,17 +468,18 @@ and you would browse to and select that directory (e.g. /home/scottrif/build/MY_QEMU_ROOTFS). + For more information on how to install the toolchain and on how to extract and install the sysroot filesystem, see the "Building an SDK Installer" section. - Select the Target Architecture: + + Select the Target Architecture: The target architecture is the type of hardware you are going to use or emulate. - Use the pull-down - Target Architecture menu + Use the pull-down "Target Architecture" menu to make your selection. The pull-down menu should have the supported architectures. @@ -473,16 +504,17 @@ emulator, or you can choose to run your image on actual hardware. - QEMU: + + QEMU: Select this option if you will be using the QEMU emulator. If you are using the emulator, you also need to locate the kernel and specify any custom options. - If you selected the - Build system derived toolchain, - the target kernel you built will be located in - the + + If you selected the Build system derived + toolchain, the target kernel you built will be + located in the Build Directory in tmp/deploy/images/machine @@ -494,10 +526,12 @@ followed by the image (e.g. /home/scottrif/poky/build/tmp/deploy/images/qemux86/bzImage-qemux86.bin). + If you selected the standalone pre-built toolchain, the pre-built image you downloaded is located in the directory you specified when you downloaded the image. + Most custom options are for advanced QEMU users to further customize their QEMU instance. These options are specified between paired @@ -514,16 +548,16 @@ The following is an example: serial ‘<-m 256 -full-screen>’ - - + Regardless of the mode, Sysroot is already defined as part of the Cross-Compiler Options - configuration in the - Sysroot Location: field. + configuration in the "Sysroot Location:" field. - External HW: + + External HW: Select this option if you will be using actual - hardware. + hardware. + @@ -558,31 +592,37 @@ To create a project based on a Yocto template and then display the source code, follow these steps: - Select "C Project" from the "File -> New" menu. + + Select "C Project" from the "File -> New" menu. - Expand Yocto Project SDK Autotools Project. + + Expand "Yocto Project SDK Autotools Project". - Select Hello World ANSI C Autotools Projects. + + Select "Hello World ANSI C Autotools Projects". This is an Autotools-based project based on a Yocto template. - Put a name in the Project name: - field. + + Put a name in the "Project name:" field. Do not use hyphens as part of the name - (e.g. hello). + (e.g. "hello"). - Click "Next". + + Click "Next". - Add appropriate information in the various - fields. + + Add appropriate information in the various fields. - Click "Finish". + + Click "Finish". - If the "open perspective" prompt appears, + + If the "open perspective" prompt appears, click "Yes" so that you are in the C/C++ perspective. - The left-hand navigation pane shows your - project. + + The left-hand navigation pane shows your project. You can display your source by double clicking the project's source file. @@ -600,7 +640,8 @@ You can override these settings for a given project by following these steps: - Select "Yocto Project Settings" from + + Select "Yocto Project Settings" from the "Project -> Properties" menu. This selection brings up the Yocto Project Settings Dialog and allows you to make changes specific to an @@ -613,22 +654,19 @@ The Yocto Project Settings Dialog allows you to override those default settings for a given project. - Make or verify your configurations for the - project and click "OK". + + Make or verify your configurations for the project and + click "OK". - Right-click in the navigation pane and - select "Reconfigure Project" from the pop-up menu. + + Right-click in the navigation pane and select + "Reconfigure Project" from the pop-up menu. This selection reconfigures the project by running - autogen.sh in the workspace for - your project. - The script also runs libtoolize, - aclocal, - autoconf, - autoheader, - automake --a, and - ./configure. - Click on the "Console" tab beneath your source code to - see the results of reconfiguring your project. + Autotools GNU utility programs + such as Autoconf, Automake, and so forth in the + workspace for your project. + Click on the "Console" tab beneath your source code + to see the results of reconfiguring your project. @@ -656,8 +694,7 @@ Select the project. - Select "Folder" from the - File > New menu. + Select "Folder" from the "File > New" menu. In the "New Folder" Dialog, select "Link to alternate @@ -782,54 +819,66 @@ exit out of or close that shell). - Select "Debug Configurations..." from the + + Select "Debug Configurations..." from the "Run" menu. - In the left area, expand - C/C++Remote Application. + + In the left area, expand + "C/C++Remote Application". - Locate your project and select it to bring + + Locate your project and select it to bring up a new tabbed view in the Debug Configurations Dialog. - Click on the "Debugger" tab to see the + + Click on the "Debugger" tab to see the cross-tool debugger you are using. Be sure to change to the debugger perspective in Eclipse. - Click on the "Main" tab. + + Click on the "Main" tab. Create a new connection to the QEMU instance by clicking on "new". - Select SSH, which means + + Select "SSH", which means Secure Socket Shell. Optionally, you can select a TCF connection instead. - Click "Next". + + Click "Next". - Clear out the "Connection name" field and + + Clear out the "Connection name" field and enter any name you want for the connection. - Put the IP address for the connection in + + Put the IP address for the connection in the "Host" field. - For QEMU, the default is 192.168.7.2. + For QEMU, the default is "192.168.7.2". However, if a previous QEMU session did not exit cleanly, the IP address increments (e.g. - 192.168.7.3). + "192.168.7.3"). You can find the IP address for the current QEMU session by looking in the xterm that opens when you launch QEMU. - Enter root, which + + Enter "root", which is the default for QEMU, for the "User" field. Be sure to leave the password field empty. Click "Finish" to close the New Connections Dialog. - If necessary, use the drop-down menu now in the + + If necessary, use the drop-down menu now in the "Connection" field and pick the IP Address you entered. - Assuming you are connecting as the root user, + + Assuming you are connecting as the root user, which is the default for QEMU x86-64 SDK images provided by the Yocto Project, in the "Remote Absolute File Path for C/C++ Application" field, browse to @@ -874,9 +923,11 @@ Be sure you change to the "Debug" perspective in Eclipse. - Click "Debug" + + Click "Debug" - Accept the debug perspective. + + Accept the debug perspective. -- cgit v1.2.3