Hi everybody,
now that CVS is back up again, we could finally add the tags for the
2.4.1 release of Bering-uClibc and test the ideas we had for how one
could build a specific release.
So, the sources in CVS are tagged (reflecting the state of CVS when
2.4.1 was released) - the tag name is "Release-2_4_1"
We also worked out (and tested) a way to build the sources from 2.4.1
without having to mess with buildtool. Here's the short version (the
slightly longer version is in the Bering uClibc developer guide in the
buildtool chapter - or should be, the next time the pages are regenerated):
If you have an SF developer account:
$ export CVS_RSH=ssh
$ mkdir /PATH/TO/WORKAREA
$ cd /PATH/TO/WORKAREA
$ cvs -z3 -d:ext:[EMAIL PROTECTED]:/cvsroot/leaf \
co -r Release-2_4_1 src/bering-uclibc
If you don't have an SF developer account:
$ mkdir /PATH/TO/WORKAREA
$ cd /PATH/TO/WORKAREA
$ cvs -z3 -d :pserver:[EMAIL PROTECTED]:/cvsroot/leaf \
co -r Release-2_4_1 src/bering-uclibc
After that, you need to modify
/PATH/TO/WORKAREA/buildtool/conf/sources.cfg so you have something like
this for the server definitions of cvs-sourceforge and
cvs-sourceforge-contrib
<Server cvs-sourceforge>
Type = file
Serverpath = /PATH/TO/WORKAREA/src/bering-uclibc/apps
</Server>
<Server cvs-contrib-sourceforge>
Type = file
Serverpath = /PATH/TO/WORKAREA/src/bering-uclibc/contrib
</Server>
After that, go to /PATH/TO/WORKAREA/buildtool, issue
./buildtool.pl build
and you should be in business.
I hope that helps - let me know if there's something I missed.
Martin
_______________________________________________
leaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
