source: README.CUSTOM@ a9ca77f

2.3 2.3.x 2.4 ablfs ablfs-more legacy new_features trunk
Last change on this file since a9ca77f was 3e7ceed, checked in by Manuel Canales Esparcia <manuel@…>, 18 years ago

Ported CUSTOM_TOOLS support to all books.

  • Property mode set to 100644
File size: 8.9 KB
RevLine 
[93d32cf]1#
2# $Id$
3#
[9a536f7]4 HOW TO ADD CUSTOM SCRIPTS TO THE JHALFS MAKEFILE
[93d32cf]5
[9a536f7]6
7 Normally JHALFS creates a Makefile containing only those scripts found in
8the {B,C,H}LFS books. An automated construction tool cannot predict the
9needs of every individual and requests are made "Can you add xxxx package".
10Rather than adding numerous package scripts and switches for each request it
11was easier to add a tool for the user(s) to code their own package needs.
12
[7b6ecc5]13 There is two areas that can be customized: how the base system is build
14and what additional configurations and packages requires your hardware to can
15boot and work with. Each one of this areas is handled in a diferent way.
16
[f222bb8]17
18
19
[7b6ecc5]20 BASE SYSTEM CUSTOMIZATION
21
22 There is two ways to alter how the base system will be built:
23
24 - Using a working copy of the book sources and editing the XML files.
25 This is the way used by book editors to test packages upgrades,
26 command changes, build order changes. etc.
27
28 This method requires you know very well the book sources and what
29 files need be edited. It will not be discussed here.
30
31 - Editing the generated build scripts to make any change you would.
32 This is the method discussed below.
33
[f222bb8]34
35 EDITING THE BASE SCRIPTS
36
37 Fisrt step is to generate the build scripts with book defaults. To do that,
38configure jhalfs activating any option you want included, but do not select
39"Run the Makefile" option.
40
41 Under the ${BUILD_DIR}/${SCRIPT_ROOT}/${PROGNAME}-commands directory
42(using the defaults values to do an LFS build, that directory name is
43/mnt/build_dir/jhalfs/lfs-commands) you will find the default build scripts.
44
45 If all you want is modify, add, or remove some command from a package
46installation, for example to change it ./configure line, just edit the related
47script. If changing or adding a patch, be sure to copy the new patch to the
48${BUILD_DIR}/sources directory. When done, run 'make' from inside the
49${BUILD_DIR}/${SCRIPT_ROOT} directory.
50
51
52 REPLACING OR INSERTING PACKAGES AND CHANGING BUILD ORDER
53
54 To remove a package from the system, just remove its script(s).
55
56 To change the version of some package to build a newest or oldest one than the
57one found in the book, edit ${BUILD_DIR}/${SCRIPT_ROOT}/pkg_tarball_list to
58change it tarball name and place the new tarball in the ${BUILD_DIR}/sources
59directory,
60
61 To replace a package by an equivalent one, rename the replaced package script
62to reflect the new package name (for example, 102-man-db -> 102-man), edit the
63script to made the required commands changes, place the new tarball in the
64${BUILD_DIR}/sources directory, and edit ${BUILD_DIR}/${SCRIPT_ROOT}/pkg_tarball_list
65file to replace the removed package tarball name by the new package tarball name.
66
67 To change the build order, rename the scripts changing the first 3-digits
68string until have it ordered in the way you want.
69
70 To insert a new package, for example to build Cracklib to can build Shadow
71with Cracklib support, first you should decide before what default package it
72need be installed, in this example before 107-shadow. Then create a new script
73containg the needed commands, using an existing one as template, and name it with
74the same 3-digits string used for that mentioned default package, but adding
75another 1-digit string. In our example, the new script to build Cracklib just
76before Shadow will be named 107-1-cracklib. This naming schema allow to insert
77up to 10 scripts before each one of the default scripts. Place the tarball for
78the new package and required patches, if any, if ${BUILD_DIR}/sources and edit
79${BUILD_DIR}/${SCRIPT_ROOT}/pkg_tarball_list to add the tarball name for that
80package.
81
82 When ready, launch again the jhalfs configuration interface. Be sure that
83are selected exactly the same options than when generating the default build
84scripts. Be sure that "Rebuild files" is unselected and select "Run the Makefile"
85if you want. Then select "Rebuild the Makefile". This will create a new Makefile
86based on the changes you made to the build scripts.
87
88
[7b6ecc5]89
90
91 ADDING POST-SYSTEM BUILD CONFIGURATION FILES AND EXTRA PACKAGES
92
93 The installation of BLFS packages is handled via blfs-tool and activated
94when you select the appropiate menu option. See README and README.BLFS for
95more info.
96
97 The feature descrbed below was added so users could install remaining
98configuration files, build the packages necessary to access the internet
99or to support specific hardware, or to install basic utilities that need
100have availables from the beginning, and was not intended to replace the BLFS
101install system.
102
[9a536f7]103
104 LAYOUT
105 A new directory has been added to JHALFS tree which will contain the
106configuration scripts and a few examples. A switch has been added to the
107configuration file which enables/disables the inclusion of personal scripts.
108
109 custom
[e7655b2]110 /config <-- where to put your scripts.
111 /examples <-- a few example scripts
112 template <-- ALL scripts MUST look like this
[9a536f7]113
114
115
116 NOTE::: You are responsible for including all dependencies and ensuring they
117 are built in the proper order.
118
119 1. To add a package to the final JHALFS Makefile you must first create a file
120 in the custom/config directory.
121 **All config files MUST follow the naming convention, xxx-PKG, where xxx
122 is the order number and PKG is the name of the package. The file naming
123 format is important as it defines the build order. The example shown
124 below has an order number 950 and log files will list in alphabetical
125 order in the /logs directory after blfs-tools scripts.
126 The simplest method is to copy the template file into the config directory
127 and rename it.
128
129 2. Populate the variables with the necessary values.
130 Variable function is self explanitory except for the inclusion of the
131 build cmds. If the package you want to include is found in the BLFS
132 book then you only need to copy/paste the cmd strings between the xEOFx
133 pairs, otherwise you will need to define the build cmds yourself.
134 NOTE::: This script you just created is not usable directly but contains
135 all the information necessary for jhalfs to create a build script
136 and an entry in the jhalfs Makefile.
137
138 3. As mentioned previously the build order is dictated by the 3 digit number
139 in the file name. If a package has dependencies it must be numerically
140 larger than the dependency files.
141 ie. The package mc has glib as a dependency and build order is
142 950-glib
143 951-mc
144
145 4. A config file for BLFS-bootscripts is already created as 999-blfs_bootscripts.
146 If a package requires a bootscript to be installed add the cmd to this
147 file and NOT in the package script. The gpm script is included as an
148 example of multiple patch files and the need for a blfs bootscript.
[93d32cf]149
[9a536f7]150
151#--------- GLIB example -----------
152
153 #
154 # Filename syntax xxx-PKG ie. 950-glibc
155 # Create a file in the custom/config directory
156 # Populate the file using the following script as an example
157 #
[93d32cf]158
[9a536f7]159PKG="glib"
160PKG_VERSION="1.2.10"
161PKG_FILE="glib-1.2.10.tar.gz"
162URL="http://gd.tuwien.ac.at/graphics/gimp/gtk/v1.2/${PKG_FILE}"
163MD5="6fe30dad87c77b91b632def29dd69ef9"
164
165 # Patches are named PATCH[1..10]
166 # This information is used to download the patch only
167 # If you do not have the MD5SUM the download will proceed with a warning.
168PATCH1="http://www.linuxfromscratch.org/patches/blfs/svn/glib-1.2.10-gcc34-1.patch 0077a1cce5e8a2231ac5a9b08c6263ba"
169
170
171 # NOTE::
172 # The convoluted scheme used to write out a temporary file is
173 # a work-around for embedded single and double quotes.
174
175( cat << "xEOFx"
176
177patch -Np1 -i ../glib-1.2.10-gcc34-1.patch &&
178./configure --prefix=/usr &&
179make
180make install &&
181chmod -v 755 /usr/lib/libgmodule-1.2.so.0.0.10
182
183xEOFx
184) > tmp
185
186
187#--------- GPM example -----------
188
189
190PKG="gpm"
191PKG_VERSION="1.20.1"
192PKG_FILE="gmp-1.20.1.tar.bz2"
193URL="ftp://arcana.linux.it/pub/gpm/gpm-1.20.1.tar.bz2"
194MD5="2c63e827d755527950d9d13fe3d87692"
195
[7b6ecc5]196 # MD5SUM is not absolutely necessary but JHALFS whines and complains
[e7655b2]197 # Add the MD5SUM if you can
[9a536f7]198PATCH1=" http://www.linuxfromscratch.org/patches/blfs/svn/gpm-1.20.1-segfault-1.patch"
199PATCH2=" http://www.linuxfromscratch.org/patches/blfs/svn/gpm-1.20.1-silent-1.patch"
200
201
202( cat << "xEOFx"
203
204patch -Np1 -i ../gpm-1.20.1-segfault-1.patch &&
205patch -Np1 -i ../gpm-1.20.1-silent-1.patch &&
206./configure --prefix=/usr --sysconfdir=/etc &&
207LDFLAGS="-lm" make
208
209make install &&
210cp -v conf/gpm-root.conf /etc &&
211ldconfig
212
213# The normal cmd to install the boot script for gpm
214# --- PUT THIS CMD INSIDE 999-blfs_bootscripts
215#make install-gpm
216
217cat > /etc/sysconfig/mouse << "EOF"
218# Begin /etc/sysconfig/mouse
219
220MDEVICE="/dev/psaux"
221PROTOCOL="imps2"
222GPMOPTS=""
223
224# End /etc/sysconfig/mouse
225EOF
226
227xEOFx
228) > tmp
229
[e7655b2]230
231#--------- CMDS ONLY example -----------
232 # This is an example of a self contained cmd script
233 # There are no referenced to a package or package dir.
234 # This method is useful for creating user files/profiles/etc
235 # at build time.
[7b6ecc5]236
[e7655b2]237
238PKG=""
239PKG_VERSION=""
240PKG_FILE=""
241URL=""
242MD5=""
243
244PATCH1=""
245
246
247( cat << "xEOFx"
248
249echo "JUST A USELESS TRACE"
250
251xEOFx
252) > tmp
253
Note: See TracBrowser for help on using the repository browser.