Contributors needed for wl500g packages

[Jean-Fabrice]

wl500g software packages are now growing through the unslung build system provided by the nslu2-linux community (cvs, build machine, hosting and many help)
I'm experiencing the build system for a few weeks and found it's now time for a "help wanted" call

So, I would like to know if any of you would be interested in contributing wl500g (and maybe so nslu2) packages using the unslung build system. That means, instead of asking for 'foo' or 'bar' packages at the wish list you would like to have on your favorite Asus toy, make 'em !

I can share my personnal knowledge on the build system and would be happy to help anyone wanting to contribute on some packages.

No developper skill is really needed to create packages. At the beginning, you should just know a few linux command (like vi, cp, rm, mv, tar, gzip), and for the rest, the 'man' and Google are good places to look at.

I may have forgotten to say Linux is mandatory to test your package. As far as I'm concerned, my laptop is my everyday job's laptop running XP.... and running Colinux on top of it (XP service). Thus, I have either XP for work and Colinux for unslung running at the same time on the same machine.

Question is now open : Are there any volunteers ?

JF

[barsju]

Well follow up the question with a quick little howto get started, and I think it would be even more tempting for people to try it out. No need to make it too detailed, just some pointers. Like what is needed (including links), and the most basic commands to get started...

If this is already on the forum, you should link to it..

S.

[macsat]

Hi

I'll be happy to give a hand in converting UNSLUNG packages to the WL500 or even creating new packages.

But....

I will need some help in getting started.

I do know linux, and I do run linux, but some "getting started" instructions might be nice !

[Jean-Fabrice]

You are both right macsat and barsju.

Here are a few more informations (some are deducted) :
The unslung build system is a set of makefiles, tools and directories, hosted at sourceforge, and used by the nslu2-linux.org developpers to improve the Linksys nslu2 (petname : slug) device : developping firmware and porting GPL softwares to it the industrialized way.

Recently, nslu2-linux.org ppl and Oleg (perhaps others) discussed together and in a joint effort, updated the original nslu2-targetted unslung build system to support our favorites toys from Asus : update of the main Makefile, make use of Oleg's provided toolchain for building Asus fw and so on.

That means that we (Asus fan guys) have now access to a powerfull build system with which we can create our packages (.ipk) and make them available for both communities (nslu2 and asus).

Now, in brief, how the unslung build system works :

1. You need, as I said previously, to have access to a x86 linux box (Colinux Debian is very convenient for me) with both original toolchain from Asus GPL tarball and last Oleg's toolchain installed.
2. Once everything is correcly installed (Asus and Oleg's toolchain sit in /opt/brcm). The next step is to get your own copy of the unslung build system on your linux using cvs checkout. Create a directory on your linux box, say /home/slug and checkout the cvs tree by running
   

   cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/nslu co unslung

   This will create a copy of the build system on your box, under /home/slug/unslung
   
   
3. Under /home/slug/unslung, you will find a bunch of directories plus a Makefile. Here is the usage of them :
   
   • CVS : use for CVS synchronisation with sourceforge repository. Not directly related to the build system
   • builds : where package are compiled/build/created
   • downloads : where original source files needed by packages are stored after being fetched from the Internet
   • make : the main directory for all the packages makefile. Files in this directory are included in the top Makefile making it know each of the existing package
   • packages : not use on your developper machine. Used on the official build system which create final package.
   • staging: use to compile depending packages when the one you are building have dependencies
   • toolchain : some tools
   • sources: if your package / makefile needs some patches or init script, you can place them here, in a subdirectory named sources/<packagename>
   • Makefile : the main Makefile where known packages are linked, where you can select your target device (nslu2 or wl500g). Usually no need to edit it very often

Creating a new package is then as simple as :

1. copying the provided make/template.mk to make/<your_package_name>.mk
2. Edit this one to fit your package
3. test it builds fine by running make <packagename>
4. test your package creates fine by running make <packagename>-ipk
5. Send me your .mk and associated sources/<packagename>/stuff for checkin in the cvs repository or create your own sourceforge id and ask rwhitby for write access to the cvs
6. Tell me when files have been checked in so I can launch a build on the official build machine which will then update wl500g packages feed

You will have understood that the most tricky part is editing you <packagename>.mk to draw the download/configure/build story of your package.
I'm still not very powerfull in that but looking at the existant makefile is a great help for tips and trick.

Now, some usefull link :

• Add A Package To Unslung :more detailed explanation on how to write your package
• Packaging Best Practices : best practices and rules for package creation
• irc.freenode.net / channel #nslu2-linux : IRC channel of nslu2-linux developpers where you can request support for package creation
• wl500 packages feeds : where wl500 packages are stored after having been built on the official build machine.

And some tips (to be grown) :

• Use the unslung build system on your linux with an unprivileged account. Creating and building a package should not require root rights. Building with a unprivilege account will show you when a software try to use root account, so you can patch it not to do so.
• often run a 'cvs update -dP' to maintain your cvs tree up to date. A lot of developpers are using the sourceforge cvs so freshing your source tree is a good idea
• for inspiration, take a look at make/nylon.mk which is my first and simple package
• for a deep test of your <packagename>.mk, run 'make distclean directories ipkg-utils <packagename>'. Doing so will ensure that your package build fine without any forgotten dependency. 'make distclean' clean the entire unslung build system by deleting directories, 'make directories' will recreate directories listed at the beginning and make ipkg-utils will install ipkg stuff needed for ipkg creation of your package.

I hope this is pretty clear. Don't hesitate to ask for help.

See you soon on #nslu2-linux

[Styno]

Nice HOWTO JF, good work !

[barsju]

Very nice indeed! Now I just need some spare time! Let me know if you have some lying around!

[oleo]

Why there are so many broken download links in the unslung CVS when I issue

make source

for nslu2 target?

Is the cause change to monotone or just nobody tracks the changes?

[rwhitby]

It's just that no-one has time to track all the sources for all the packages. Once they are built and in the feeds, then it's up to individual package contributors (or users) to notice that there is a new version and update to it.

BTW, we have re-arranged the optware makefile so that new packages by default attempt to be built for wl500g. This means that new packages may appear by magic without any intervention by JF or myself.

In doing so, we worked out how to build a whole lot more wl500g packages. In particular, those who have been looking for MySQL might find a Christmas present in the feed ...

http://ipkg.nslu2-linux.org/feeds/op...ross/unstable/

-- Rod (nslu2-linux project lead, and Optware infrastructure developer)

[oleo]

I mean that old download sources are lagging in download directory of the build machine. There is no instrument to check if the file is available for download or not. This introduces a big problem for newcomers as a lot of packages are deleted with a new version. And this is not tracked by Makefile. Such packages should be tagged somehow in Makefile. Or erase the download dir from time to time to look for NEED_TO_BE_FIXED packages!

______________________________
waiting for uclibc-stdlibc++

[digimic]

can we have a package for mysql extension which works on OLEG's firmware?

[Jean-Fabrice]

can we have a package for mysql extension which works on OLEG's firmware?

see http://wl500g.info/showpost.php?p=14559&postcount=9

[DrChair]

I've managed to make a few packages, and fixed a few errors in some other ones.

new: sabnzbd.mk and py-yenc.mk
fixed : py-elementtree.mk, py-cherrypy.mk and automake.mk

What is easiest way to get them into the feed?

btw the only thing I changed in py-elementtree and py-cherrypy is the staging part. There was none, but needed for sabnzbd.mk.
Should the ipkg version be increased for that??

[rwhitby]

I've managed to make a few packages, and fixed a few errors in some other ones.

new: sabnzbd.mk and py-yenc.mk
fixed : py-elementtree.mk, py-cherrypy.mk and automake.mk

What is easiest way to get them into the feed?

btw the only thing I changed in py-elementtree and py-cherrypy is the staging part. There was none, but needed for sabnzbd.mk.
Should the ipkg version be increased for that??

The easiest way is to follow the instructions at http://www.nslu2-linux.org/wiki/Optw...ckageToOptware, and then we'll be happy to give you write access to the repository.

It is always a good idea to change the ipkg version for any change in the build.

-- Rod

[Oyabun]

Hello folks.
I was thinking about to offer my help, but I'm not a linux whit. To be more exact I can get along with the wl500, following the guides - and make some educated guesses along the way to make it better suited to my needs - but I consider myself more of a power user than a programmer or sysadmin.
I've started to install a colinux on my notebook - but I have no experience with it so far.
So until I can get to a point to be able to compile my own packages I ask someone of you to go and take a look here please: help to compile esniper
Thank you in advance
Oya

[rwhitby]

I've started to install a colinux on my notebook - but I have no experience with it so far.

I would suggest using VMware server (which is now free) and ubuntu instead of CoLinux.

-- Rod