OpenEmbedded Tools for Eclipse (OTE)
|NOTE: This page has been identified as having content that is significantly out-of-date, usually because it refers to OpenEmbedded-Classic - for new projects, you should use OpenEmbedded-Core.
See OpenEmbedded Wiki Update Project for more details.
- 1 Overview
- 2 Status
- 3 Workflow
- 3.1 Install OpenEmbedded
- 3.2 Import Existing OE into Workspace
- 3.3 Create Recipe
- 3.4 Edit Recipe
- 3.5 Build Recipe
- 3.6 Import Recipe Sources as New Project
- 3.7 Browse OE variables
- 4 Contact
OpenEmbedded Tools for Eclipse (OTE) is a set of Eclipse plugins to make using OpenEmbedded from within Eclipse possible. This page describes a set of workflows that perform common OpenEmbedded tasks, as well as the current state of development of the plugins.
OTE is in a beta form. Functionality present within the plugins should work well, but development on them is fairly new. Bugs are expected!
- Invalid thread access in console view when starting build.
- No longer use "-b" option in Bitbake to specify build recipe, due to
problems in Bitbake.
- Deprecate outdated Bug Labs Linux installer option.
- Update OpenEmbedded Dev installer option with newer bitbake and
- "Import recipe as project" feature relies on "bitbake -b" option.
In recent Bitbake versions, this feature is broken, so the Eclipse action is also broken.
- Numerous fixes in Create Project Wizard to sync to latest OE-Dev install.
OTE is licensed under the Eclipse Public License (EPL).
Sources are available at svn://svn.buglabs.net/ote/trunk.
The OTE updatesite, used to install the plugins from within Eclipse:
OTE is designed to facilitate a set of typical actions or tasks that an OE developer would do.
4. Assuming all the necessary system tools are available, the wizard will download sources and configure your new OpenEmbedded install.
5. Now by clicking finish, an Eclipse project will be created. It may take a few moments for Eclipse to index all the files in the project. Your workbench should look something like this:
Import Existing OE into Workspace
To access the Import Project wizard, select File -> Import... and select the Import OpenEmbedded Project wizard from the general dialog like so:
Next fill in the three fields required for importing the project.
- Name: this is the name of the Eclipse project in your workspace and can be anything.
- Location: this is the base directory of your OpenEmbedded project.
- Init Script: this is the shell script that initializes OE environment variables and updates the path.
The final wizard page shows the output of what you would see in the terminal after executing bitbake -e.
After clicking finish a new project should be available in your workspace. Depending on your machine it may take some moments for Eclipse to scan the entire set of files. It is important to note that even though the project appears in your Eclipse workspace, the files are accessed from your OE project root. So, modifications to these files will be reflected in your existing OE install.
This simple wizard generates a template recipe file based on fields that are entered by the user. The wizard can be accessed via File -> New... and selecting New OpenEmbedded Recipe from the dialog. Here is what the wizard looks like:
Now by entering the fields and selecting Finish a new recipe will be generated. Note that currently the Location field must contain a valid directory, so if you're creating a completely new recipe you'll need to create the directory before running this wizard. Here is an example of a recipe filled out:
After clicking Finish Eclipse will open an editor on the generated file. Here is an example:
From here the user can add necessary details to the recipe for building.
Recipes can be selected in the Navigator view by opening the recipes or packages directory in your OpenEmbedded install. Any file with a .bb, .inc or .conf extension will be loaded by the BitBake editor. This editor offers the following features.
Eclipse offers a nice file selection dialog that allows for files to be quickly edited without navigating through many folders. This dialog is activated with ctrl-shift-r. The 'r' stands for resource, Eclipse terminology for a file. In this dialog begin typing the file you want to edit. Wildcards and regular expressions are supported. Previously edited files are already available. Here is a screenshot of the dialog:
The recipe file in the editor will color various sections of the recipe. For example comments will be green, variable declarations will be blue.
Some conventional variables are available by hitting ctrl-space in the editor window. Here is a screenshot of the context menu:
The bitbake editor will create a template function or addtask declaration when selected from the ctrl-space menu.
Hover-over Variable Information
The bitbake editor will show the value of previously declared variables when the mouse is put over them. The appear as tooltip text. Here is an example of this feature:
A package can be generated from Eclipse via the toolbar or the context menu. This function essentially calls bitbake -b <selected package> to perform the build. The output of the bitbake command will be displayed in the console view.
Import Recipe Sources as New Project
This allows application developers to create a source project from an OpenEmbedded recipe. This is a simple way to begin modifying a project from within Eclipse. Other Eclipse plugins such as CDT (C/C++ development tools) or PyDev (Python development tools) may be used with these imported projects. However automatic integration is not supported from within OTE and adding appropriate project natures will either need to be done from within the respective plugin or manually by editing the .project file in your project.
Browse OE variables
OTE provides a quick way of viewing and searching through BitBake/OE variables. The wizard is activate from the OTE toolbar and looks like this:
Please see the OTE Google Group for questions or problems with OTE.