It is often the case that some module of gPXE is only relevant if the subsystem it depends on is already being included. For instance, commands to manage wireless interfaces are quite useless if no compiled-in driver has pulled in the wireless networking stack. There may be a user-modifiable configuration options for these dependent modules, but even if enabled, they should not be included when they would be useless. Solve this by allowing the creation of config_subsystem.c, for configuration directives like those in the global config.c that should only be considered when subsystem.c is included in the final gPXE build. For consistency, move core/config.c to the config/ directory, where the other config_subsystem.c files will eventually reside. Signed-off-by: Marty Connor <mdc@etherboot.org>tags/v1.0.0-rc1
|
||
73 | 73 |
|
74 | 74 |
|
75 | 75 |
|
76 |
|
|
76 | 77 |
|
77 | 78 |
|
78 | 79 |
|
|
||
10 | 10 |
|
11 | 11 |
|
12 | 12 |
|
13 |
|
|
14 |
|
|
15 |
|
|
16 |
|
|
17 |
|
|
18 |
|
|
19 |
|
|
20 |
|
|
21 |
|
|
22 |
|
|
23 |
|
|
24 |
|
|
25 |
|
|
26 |
|
|
27 |
|
|
28 |
|
|
29 |
|
|
30 |
|
|
13 | 31 |
|
14 | 32 |
|
15 | 33 |
|
|
||
159 | 159 |
|
160 | 160 |
|
161 | 161 |
|
162 |
|
|
163 |
|
|
162 | 164 |
|
163 | 165 |
|
164 | 166 |
|
165 | 167 |
|
168 |
|
|
169 |
|
|
170 |
|
|
166 | 171 |
|
167 | 172 |
|
168 | 173 |
|