-
OpenPandora: Development toolchains, SDK’s and build platforms (Part 2).
This is the 2nd of the 2 simple guides I have put together to help you through the process of getting a working development environment and basic SDK going for the OpenPandora allowing you to build applications, compile up code, all of that neat stuff really.
Note: These guides and toolchain/SDK packages do not constitute an ‘official’ OpenPandora SDK or anything of the sort, they are just what I have put together during the development process in the hope somebody may find it useful.
There will be things missing libs and odd littke things that did not end up in the SDK package etc. at first and this article and the toolchains will evolve as time goes on.
Consider this 2nd part of the guide a work in progress.
With the OpenPandora you have 2 primary options for code development…
Want to write code for the OpenPandora on the OpenPandora, have a little read of this. Not the way I would recommend doing normal development but handy sometimes.
The is covered in part 1 of this article.
- Cross compiling
The most common method of code development for a device such as the OpenPandora. Requires access to a regular PC to using for building code.
The is covered by this part of the article.
I’ll aim to outline how you can start to develop code using either setup, and provide a really simple test app to prove your setup is working.
This is mainly aimed at C, C++ and Assembler developers who are familiar with GCC, build tools and Linux in general.
-
OpenPandora: Development toolchains, SDK’s and build platforms (Part 1).
This is the 1st of 2 posts that I hope will form simple guides to help you through the process of getting a working development environment and basic SDK setup for the OpenPandora allowing you to build applications, compile up code, all of that neat stuff really.
Note: These guides and toolchain/SDK packages do not constitute any ‘official’ OpenPandora SDK or anything of the sort, they are just what I have put together during the development process in the hope somebody may find it useful.
Some of the information in these articles has already been covered, I just got tired of covering the same ground helping people so I figured I could refer them here so everyone benefits.
With the OpenPandora you have 2 primary options for code development…
- Native (on device) software development
Want to write code for the OpenPandora on the OpenPandora, have a little read of this. Not the way I would recommend doing normal development but handy sometimes.
The is covered by this part of the article.
The most common method of code development for a device such as the OpenPandora. Requires access to a regular PC to using for building code.
The is covered in part 2 of this article.
I’ll aim to outline how you can start to develop code using either setup, and provide a really simple test app to prove your setup is working.
This is mainly aimed at C, C++ and Assembler developers who are familiar with GCC, build tools and Linux in general.
Native (on device) software development:
-
OpenPandora: Building your own ROOTFS image (Part 1).
Updated: 7th June to expand the setup scripts section and tell people to get them from GIT.
This is the 1st of 2 articles I will be publishing on getting started with building the Linux distribution installed on the OpenPandora, from source code, from scratch.
Note: This is not a guide to using OpenEmbedded or bitbake, or writing package recipes. It’s just a guide to getting an OpenPandora build setup running.
This 1st article will cover the basic setup of OpenEmbedded environment and the building of our Ångström distribution derived ROOTFS, the 2nd will detail how you can run the resulting images on your OpenPandora from SD cards, or if you really want to, the NAND.
I also plan to write a separate related article will show how you can setup toolchains and SDK’s to help you develop applications for (and natively on) the OpenPandora using some of the strengths of OpenEmbedded to make this easier.
As I write these posts in my own time I can’t promise to do anything quickly. Nor can I make any promises about how accurate they may be
. As always, feedback is welcome.Most application developers/porters will only be interested in the related article on setting up SDK’s and toolchains, these 2 are really for the hardened Linux hackers who want to mess about with the ROOTFS/distribution development.
Health (and sanity) warning: Building the entire ROOTFS from scratch is pretty technical in nature, if you have no desire to rebuild the ROOTFS or hack with the inner workings of you’re OpenPandora this is probably not for you.
You can’t really damage anything on your OpenPandora but if your not familiar with compiling your own apps, kernels etc. and fixing things when they don’t work this will present a VERY steep learning curve. You also have the potential to make a mess of your build host if you are not careful with the setup.
I’ll focus showing how you can build a ‘one <> one’ version of the 1st official release (GIT tag: “Release-2010-05/1”).
Once you have that going feel free to build the tips of the metadata GIT’s if you want to work with the latest and greatest or get stuck in modifying the metadata to suit whatever purpose you may have in mind.
Recent Comments