Changes between Version 10 and Version 11 of BuildLibc


Ignore:
Timestamp:
Jan 22, 2006, 7:26:08 PM (14 years ago)
Author:
bird
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BuildLibc

    v10 v11  
    2121which will create a directory called trunk and mirror the Netlabs trunk repositry. For other interesting targets see Select Source Tree.
    2222
     23If you check out the thunk you will need kBuild. kBuild is not converted to svn yet, so you'll have to dig up a working cvs client.
     24What to do:
     25 1. Go to the root dir in the trunk checkout.
     26 1. cvs -d :pserver:guest@cvs.netlabs.org:/netlabs.cvs/kbuild login [[BR]]Password: readonly
     27 1. cvs -d :pserver:guest@cvs.netlabs.org:/netlabs.cvs/kbuild co kBuild
     28
    2329
    2430= Setting Up The Build Environment =
     
    3642= Doing The Build =
    3743
    38 The instructions here is somewhat different between the trunk and the branches. Things has moved around and some even split up after libc-0.6 was branched.
     44The instructions differents between the trunk and the branches. The repository is begin reorganized after the libc-0.6 release branch was created and is currently in the process of being switched over to a different build system (at least the non gnu bits).
    3945
    4046== Building The Trunk ==
    4147
    4248You have two choices, build everything or just a single component.
    43 When building single components you go into the root directory for that component. For libc that means /libc. libc and emx are currently in an intermediate shape buildsystem wise, and you'll have to specify the makefile on the make commandline: {{{ make -f Makefile.gmk }}}  This will print a menu of the make goals. The {{{ all }}} and {{{ install }}} goals are choices you can't go wrong with.
     49When building single components you go into the root directory for that component. For libc that means /libc.
     50
     51
     52libc and emx are currently in an intermediate shape buildsystem wise, and you'll have to specify the makefile on the make commandline: {{{ make -f Makefile.gmk }}}  This will print a menu of the make goals. The {{{ all }}} and {{{ install }}} goals are choices you can't go wrong with.
    4453
    4554Building gcc and binutils means using the GNU buildsystem. Explain about the GNU buildsystem, blah blah blah.