|
2
|
1 |
|
|
|
2 |
This workspace contains examples of building open source software components using three methodologies. In the spec-files directory, the pkgbuild is use to build the components from a RPM spec file based build. In the components directory, a make(1) based build is used.
|
|
|
3 |
|
|
|
4 |
spec-files
|
|
|
5 |
spec based build
|
|
|
6 |
|
|
|
7 |
components
|
|
|
8 |
GNU make based build(s)
|
|
|
9 |
|
|
|
10 |
make-rules
|
|
|
11 |
Shared rules to include in component specific makefiles (instructions)
|
|
|
12 |
|
|
|
13 |
make-rules/configure.mk
|
|
|
14 |
shared rules for components using GNU auto* tools to build
|
|
|
15 |
|
|
|
16 |
make-rules/ips.mk
|
|
|
17 |
shared rules for packaging under IPS
|
|
|
18 |
|
|
|
19 |
make-rules/prep.mk
|
|
|
20 |
shared rules for downloading, unpacking, and patching component
|
|
|
21 |
source.
|
|
|
22 |
|
|
|
23 |
make-rules/setup.py.mk
|
|
|
24 |
shared rules for components using python setup.py to build
|
|
|
25 |
|
|
|
26 |
make-rules/shared-macros.mk
|
|
|
27 |
common macros that apply to building many things.
|
|
|
28 |
|
|
|
29 |
tools
|
|
|
30 |
shared tools for building components
|
|
|
31 |
|
|
|
32 |
transforms
|
|
|
33 |
shared pkgmogrify(1) transformations to apply to packages as they are
|
|
|
34 |
being built and published
|
|
|
35 |
|
|
|
36 |
|
|
|
37 |
To build uing the GNU make based build you can
|
|
|
38 |
$ WS_TOP=$(pwd) ; cd components ; gmake -j 4 publish
|
|
|
39 |
This will construct a files based repository for publishing, create a log directory, build the components (4 at a time) and publish them to the repo. Logs of each component build will go in the logs directory
|
|
|
40 |
|