Changes between Version 10 and Version 11 of BuildLibc
- Timestamp:
- Jan 22, 2006, 7:26:08 PM (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BuildLibc
v10 v11 21 21 which will create a directory called trunk and mirror the Netlabs trunk repositry. For other interesting targets see Select Source Tree. 22 22 23 If 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. 24 What 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 23 29 24 30 = Setting Up The Build Environment = … … 36 42 = Doing The Build = 37 43 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.44 The 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). 39 45 40 46 == Building The Trunk == 41 47 42 48 You 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. 49 When building single components you go into the root directory for that component. For libc that means /libc. 50 51 52 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. 44 53 45 54 Building gcc and binutils means using the GNU buildsystem. Explain about the GNU buildsystem, blah blah blah.
