From 395486f638b31e7c74ecd12e7fd8f79ad4e00a00 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 19 Sep 2013 22:29:37 -0700 Subject: [PATCH] dev-manual: First pass changes to support Kepler Eclipse First pass at changes to support Eclipse Kepler 4.3 release. (From yocto-docs rev: 265bc3f4ae3442b2fd0490d0f4558c7a584cb31c) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-model.xml | 90 ++++++------------- 1 file changed, 28 insertions(+), 62 deletions(-) diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml index 3474d05546..a2dabf0185 100644 --- a/documentation/dev-manual/dev-manual-model.xml +++ b/documentation/dev-manual/dev-manual-model.xml @@ -667,9 +667,6 @@ However, if you currently have the Juno 4.2 version installed and you do not want to upgrade the IDE, you can configure Juno to work with the Yocto Project. - See the - "Configuring the Eclipse IDE (Juno)" - section. @@ -696,19 +693,17 @@ -
- Configuring the Eclipse IDE (Kepler) +
+ Configuring the Eclipse IDE This section presents the steps needed to configure the - Kepler 4.3 Eclipse IDE. - If you are using Juno 4.2, see the - "Configuring the Eclipse IDE (Juno)". + Eclipse IDE. Before installing and configuring the Eclipse Yocto Plug-in, - you need to configure the Kepler 4.3 Eclipse IDE. + you need to configure the Eclipse IDE. Follow these general steps: Start the Eclipse IDE. @@ -716,8 +711,12 @@ select "Install New Software" from the "Help" pull-down menu. Select - Juno - &ECLIPSE_JUNO_URL; + Kepler - &ECLIPSE_KEPLER_URL; from the "Work with:" pull-down menu. + + For Juno, select + Juno - &ECLIPSE_JUNO_URL; + Expand the box next to "Linux Tools" and select the @@ -744,52 +743,6 @@
-
- Configuring the Eclipse IDE (Juno) - - - This section presents the steps needed to configure the - Juno 4.2 Eclipse IDE. - - - - Before installing and configuring the Eclipse Yocto Plug-in, - you need to configure the Juno 4.2 Eclipse IDE. - Follow these general steps: - - Start the Eclipse IDE. - Make sure you are in your Workbench and - select "Install New Software" from the "Help" - pull-down menu. - Select - Juno - &ECLIPSE_JUNO_URL; - from the "Work with:" pull-down menu. - - Expand the box next to "Linux Tools" - and select the - LTTng - Linux Tracing Toolkit boxes. - - Expand the box next to "Mobile and - Device Development" and select the following boxes: - - C/C++ Remote Launch - Remote System Explorer End-user Runtime - Remote System Explorer User Actions - Target Management Terminal - TCF Remote System Explorer add-in - TCF Target Explorer - - Expand the box next to "Programming - Languages" and select the - Autotools Support for CDT - and C/C++ Development Tools - boxes. - Complete the installation and restart - the Eclipse IDE. - - -
-
Installing or Accessing the Eclipse Yocto Plug-in @@ -819,17 +772,25 @@ Click "Add..." in the "Work with:" area. Enter - &ECLIPSE_DL_PLUGIN_URL; + &ECLIPSE_DL_PLUGIN_URL;/kepler in the URL field and provide a meaningful name - in the "Name" field. + in the "Name" field. + + If you are using Juno, use + &ECLIPSE_DL_PLUGIN_URL;/juno + in the URL 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. - Check the box next to - Development tools and SDKs for Yocto Linux. + Check the boxes next to + Yocto Project ADT Plug-in, + Yocto Project Bitbake Commander Plug-in, + and + Yocto Project Documentation plug-in. Complete the remaining software installation steps and then restart the Eclipse @@ -849,8 +810,13 @@ Open a shell and create a Git repository with: - $ git clone git://git.yoctoproject.org/eclipse-poky yocto-eclipse + $ git clone git://git.yoctoproject.org/eclipse-poky-kepler yocto-eclipse + + If you are using Juno, the repository is + located at + git://git.yoctoproject.org/eclipse-poky-juno. + For this example, the repository is named ~/yocto-eclipse. @@ -1129,7 +1095,7 @@ Build system derived toolchain, the target kernel you built will be located in the Build Directory in - tmp/deploy/images + tmp/deploy/images/<machine> directory. If you selected Standalone pre-built toolchain,