35 source code management system, but it does not retrieve the community |
35 source code management system, but it does not retrieve the community |
36 source archives associated with the gate content. To download the |
36 source archives associated with the gate content. To download the |
37 community source associated with your cloned workspace, you will need to |
37 community source associated with your cloned workspace, you will need to |
38 execute the following: |
38 execute the following: |
39 |
39 |
40 $ export WS_TOP=/scratch/clone |
|
41 $ cd /scratch/clone/components |
40 $ cd /scratch/clone/components |
42 $ gmake download |
41 $ gmake download |
43 |
42 |
44 This will use GNU make and the downloading tool in the gate to walk through |
43 This will use GNU make and the downloading tool in the gate to walk through |
45 all of the component directories downloading and validating the community |
44 all of the component directories downloading and validating the community |
53 archive. |
52 archive. |
54 |
53 |
55 Building the Bits. |
54 Building the Bits. |
56 |
55 |
57 You can build individual components or the contents of the entire gate. |
56 You can build individual components or the contents of the entire gate. |
58 Regardless of how you build the gate, you must set WS_TOP in the calling |
|
59 environment to point to the top of your workspace. Ex: |
|
60 |
|
61 $ export WS_TOP=/scratch/clone |
|
62 |
57 |
63 Component build |
58 Component build |
64 |
59 |
65 If you are only working on a single component, you can just build it using |
60 If you are only working on a single component, you can just build it using |
66 following: |
61 following: |
67 |
62 |
68 setup the workspace for building components |
63 setup the workspace for building components |
69 |
64 |
70 $ cd ${WS_TOP}/components ; gmake setup |
65 $ cd (your-workspace)/components ; gmake setup |
71 |
66 |
72 build the individual component |
67 build the individual component |
73 |
68 |
74 $ cd (component-dir) ; gmake publish |
69 $ cd (component-dir) ; gmake publish |
75 |
70 |
76 Complete Top Down build |
71 Complete Top Down build |
77 |
72 |
78 Complete top down builds are also possible by simply running |
73 Complete top down builds are also possible by simply running |
79 |
74 |
80 $ cd ${WS_TOP}/components |
75 $ cd (your-workspace)/components |
81 $ gmake package-install |
76 $ gmake publish |
82 |
77 |
83 The 'package-install' target will build each component, publish it to the |
78 The 'publish' target will build each component and publish it to the |
84 workspace IPS repo and install it in the running environment. As a result, |
79 workspace IPS repo. |
85 it is strongly recommended that you only perform complete top down builds |
80 Tools to help facilitate build zone creation will be integrated |
86 in a zone. Tools to help facilitate build zone creation will be integrated |
|
87 shortly. If the zone you create to build your workspace in does not have |
81 shortly. If the zone you create to build your workspace in does not have |
88 networking enabled, you can pre-download any community source archives into |
82 networking enabled, you can pre-download any community source archives into |
89 your workspace from the global with: |
83 your workspace from the global with: |
90 |
84 |
91 $ cd ${WS_TOP}/components |
85 $ cd (your-workspace)/components |
92 $ gmake download |
86 $ gmake download |
93 |
87 |
94 You can add parallelism to your builds by adding '-j (jobs)' to your gmake |
88 You can add parallelism to your builds by adding '-j (jobs)' to your gmake |
95 command line arguments. |
89 command line arguments. |
96 |
90 |