NSLU2-Linux
view · edit · print · history

OpenSlug.AddingPackages History

Hide minor edits - Show changes to markup

April 25, 2008, at 05:17 AM by joe --
Deleted lines 5-6:

Before getting started building packages for SlugOS, you'll need to setup openembedded, which can be found here. You'll want to set DISTRO = "slugos" and MACHINE = "nslu2be" (le if you're using little endian) in your local.conf

April 25, 2008, at 05:16 AM by slithy --
Changed lines 6-7 from:

Before getting started building packages for SlugOS, you'll need to setup openembedded, which can be found here: http://oe.linuxtogo.org/wiki/GettingStarted. You'll want to set DISTRO = "slugos" and MACHINE = "nslu2be" (le if you're using SlugOSLe?) in your local.conf

to:

Before getting started building packages for SlugOS, you'll need to setup openembedded, which can be found here. You'll want to set DISTRO = "slugos" and MACHINE = "nslu2be" (le if you're using little endian) in your local.conf

April 25, 2008, at 05:14 AM by slithy -- added info about setting up OE
Added lines 6-7:

Before getting started building packages for SlugOS, you'll need to setup openembedded, which can be found here: http://oe.linuxtogo.org/wiki/GettingStarted. You'll want to set DISTRO = "slugos" and MACHINE = "nslu2be" (le if you're using SlugOSLe?) in your local.conf

November 16, 2006, at 01:56 AM by fcarolo -- reorganizing information about Optware packages
Changed lines 4-5 from:
to:
November 16, 2006, at 01:56 AM by fcarolo -- reorganizing information about Optware packages
Changed lines 4-5 from:
to:
February 05, 2006, at 06:16 PM by eFfeM --
Changed lines 1-2 from:

Adding packages to OpenSlug

to:

Adding packages to SlugOS

Changed lines 10-12 from:

This is the case if the package is listed in openembedded/packages but is not present yet. This means that the basic work is done (e.g. the bitbake files are there).

In this case you need to add the package to openembedded/conf/distro/openslug-packages.conf

to:

This is the case if the package is listed in the openembedded/packages directory but is not present yet in the feed. This means that the basic work is done (e.g. the bitbake files are there).

In this case you need to add the package to openembedded/conf/distro/slugos-packages.conf

September 11, 2005, at 11:28 AM by koen -- add missing @@
Changed lines 13-14 from:

After doing that (and of course source setup-env), you can issue the command bitbake <package>@@ to compile the package. Preferably this is done by cross-compilation.

to:

After doing that (and of course source setup-env), you can issue the command bitbake <package> to compile the package. Preferably this is done by cross-compilation.

September 11, 2005, at 11:19 AM by eFfeM -- creation
Added lines 1-24:

Adding packages to OpenSlug

This is a brief note on how to add a new package to OpenSlug. You might also want to read AddAPackageToUnslung.

There are two different scenarios, depending on whether you want to add an already existing but not tested package or whether the package that you want to add is completely new. Each scenario is described in a different section.

Adding an already existing package

This is the case if the package is listed in openembedded/packages but is not present yet. This means that the basic work is done (e.g. the bitbake files are there).

In this case you need to add the package to openembedded/conf/distro/openslug-packages.conf After doing that (and of course source setup-env), you can issue the command bitbake <package>@@ to compile the package. Preferably this is done by cross-compilation.

After installing the generated package can be found in tmp/deploy/ipk. Install it on your slug and test your work. If there are problems fix and test them until everything is ok.

When everything is fine go to the #openslug channel on irc.freenode.net and ask how to submit your package.

Adding a completely new package

Adding a complete new package is more complicated. You'll need to create a directory in openembedded/packages for the package and carve the required .bb files, add patches etc. etc. Probably the quickest way to start is to look at a similar package and copy and adapt its files.

After doing that of course you still need to build and test the package as outlined in the step before. Again you might find help in #openslug channel on irc.freenode.net

view · edit · print · history · Last edited by joe.
Based on work by slithy, fcarolo, eFfeM, and koen.
Originally by eFfeM.
Page last modified on April 25, 2008, at 05:17 AM