]>
Commit | Line | Data |
---|---|---|
44eb65ce RL |
1 | Intro |
2 | ===== | |
3 | ||
4 | This directory contains a few sets of files that are used for | |
5 | configuration in diverse ways: | |
6 | ||
7 | *.conf Target platform configurations, please read | |
8 | 'Configurations of OpenSSL target platforms' for more | |
9 | information. | |
10 | *.tmpl Build file templates, please read 'Build-file | |
11 | programming with the "unified" build system' as well | |
12 | as 'Build info files' for more information. | |
13 | *.pm Helper scripts / modules for the main `Configure` | |
14 | script. See 'Configure helper scripts for more | |
15 | information. | |
16 | ||
17 | ||
9e0724a1 | 18 | Configurations of OpenSSL target platforms |
ddf1847d | 19 | ========================================== |
9e0724a1 | 20 | |
225f980d | 21 | Configuration targets are a collection of facts that we know about |
9e0724a1 RL |
22 | different platforms and their capabilities. We organise them in a |
23 | hash table, where each entry represent a specific target. | |
24 | ||
225f980d RL |
25 | Note that configuration target names must be unique across all config |
26 | files. The Configure script does check that a config file doesn't | |
27 | have config targets that shadow config targets from other files. | |
28 | ||
9e0724a1 RL |
29 | In each table entry, the following keys are significant: |
30 | ||
31 | inherit_from => Other targets to inherit values from. | |
32 | Explained further below. [1] | |
33 | template => Set to 1 if this isn't really a platform | |
34 | target. Instead, this target is a template | |
35 | upon which other targets can be built. | |
36 | Explained further below. [1] | |
37 | ||
38 | sys_id => System identity for systems where that | |
39 | is difficult to determine automatically. | |
40 | ||
906eb3d0 RL |
41 | enable => Enable specific configuration features. |
42 | This MUST be an array of words. | |
43 | disable => Disable specific configuration features. | |
44 | This MUST be an array of words. | |
45 | Note: if the same feature is both enabled | |
46 | and disabled, disable wins. | |
47 | ||
310f28df RL |
48 | as => The assembler command. This is not always |
49 | used (for example on Unix, where the C | |
50 | compiler is used instead). | |
51 | asflags => Default assembler command flags [4]. | |
8c3bc594 RL |
52 | cpp => The C preprocessor command, normally not |
53 | given, as the build file defaults are | |
54 | usually good enough. | |
310f28df | 55 | cppflags => Default C preprocessor flags [4]. |
8c3bc594 | 56 | defines => As an alternative, macro definitions may be |
310f28df RL |
57 | given here instead of in `cppflags' [4]. |
58 | If given here, they MUST be as an array of | |
59 | the string such as "MACRO=value", or just | |
8c3bc594 RL |
60 | "MACRO" for definitions without value. |
61 | includes => As an alternative, inclusion directories | |
310f28df RL |
62 | may be given here instead of in `cppflags' |
63 | [4]. If given here, the MUST be an array | |
64 | of strings, one directory specification | |
65 | each. | |
ea241958 | 66 | cc => The C compiler command, usually one of "cc", |
9e0724a1 RL |
67 | "gcc" or "clang". This command is normally |
68 | also used to link object files and | |
69 | libraries into the final program. | |
ea241958 RL |
70 | cxx => The C++ compiler command, usually one of |
71 | "c++", "g++" or "clang++". This command is | |
72 | also used when linking a program where at | |
73 | least one of the object file is made from | |
74 | C++ source. | |
310f28df RL |
75 | cflags => Defaults C compiler flags [4]. |
76 | cxxflags => Default C++ compiler flags [4]. If unset, | |
77 | it gets the same value as cflags. | |
9e0724a1 | 78 | |
c86ddbe6 RL |
79 | (linking is a complex thing, see [3] below) |
80 | ld => Linker command, usually not defined | |
9e0724a1 RL |
81 | (meaning the compiler command is used |
82 | instead). | |
83 | (NOTE: this is here for future use, it's | |
84 | not implemented yet) | |
310f28df RL |
85 | lflags => Default flags used when linking apps, |
86 | shared libraries or DSOs [4]. | |
c86ddbe6 | 87 | ex_libs => Extra libraries that are needed when |
310f28df | 88 | linking shared libraries, DSOs or programs. |
edc79fc9 AP |
89 | The value is also assigned to Libs.private |
90 | in $(libdir)/pkgconfig/libcrypto.pc. | |
310f28df RL |
91 | |
92 | shared_cppflags => Extra C preprocessor flags used when | |
93 | processing C files for shared libraries. | |
94 | shared_cflag => Extra C compiler flags used when compiling | |
95 | for shared libraries, typically something | |
96 | like "-fPIC". | |
97 | shared_ldflag => Extra linking flags used when linking | |
98 | shared libraries. | |
99 | module_cppflags | |
100 | module_cflags | |
101 | module_ldflags => Has the same function as the corresponding | |
102 | `shared_' attributes, but for building DSOs. | |
103 | When unset, they get the same values as the | |
104 | corresponding `shared_' attributes. | |
9e0724a1 | 105 | |
9e0724a1 RL |
106 | ar => The library archive command, the default is |
107 | "ar". | |
108 | (NOTE: this is here for future use, it's | |
109 | not implemented yet) | |
110 | arflags => Flags to be used with the library archive | |
6475b649 RL |
111 | command. On Unix, this includes the |
112 | command letter, 'r' by default. | |
9e0724a1 RL |
113 | |
114 | ranlib => The library archive indexing command, the | |
115 | default is 'ranlib' it it exists. | |
116 | ||
117 | unistd => An alternative header to the typical | |
118 | '<unistd.h>'. This is very rarely needed. | |
119 | ||
120 | shared_extension => File name extension used for shared | |
df443918 | 121 | libraries. |
9e0724a1 RL |
122 | obj_extension => File name extension used for object files. |
123 | On unix, this defaults to ".o" (NOTE: this | |
124 | is here for future use, it's not | |
125 | implemented yet) | |
126 | exe_extension => File name extension used for executable | |
127 | files. On unix, this defaults to "" (NOTE: | |
128 | this is here for future use, it's not | |
129 | implemented yet) | |
822b5e26 VD |
130 | shlib_variant => A "variant" identifier inserted between the base |
131 | shared library name and the extension. On "unixy" | |
132 | platforms (BSD, Linux, Solaris, MacOS/X, ...) this | |
133 | supports installation of custom OpenSSL libraries | |
134 | that don't conflict with other builds of OpenSSL | |
135 | installed on the system. The variant identifier | |
136 | becomes part of the SONAME of the library and also | |
137 | any symbol versions (symbol versions are not used or | |
138 | needed with MacOS/X). For example, on a system | |
139 | where a default build would normally create the SSL | |
140 | shared library as 'libssl.so -> libssl.so.1.1' with | |
141 | the value of the symlink as the SONAME, a target | |
142 | definition that sets 'shlib_variant => "-abc"' will | |
143 | create 'libssl.so -> libssl-abc.so.1.1', again with | |
144 | an SONAME equal to the value of the symlink. The | |
145 | symbol versions associated with the variant library | |
146 | would then be 'OPENSSL_ABC_<version>' rather than | |
147 | the default 'OPENSSL_<version>'. The string inserted | |
148 | into symbol versions is obtained by mapping all | |
149 | letters in the "variant" identifier to upper case | |
150 | and all non-alphanumeric characters to '_'. | |
9e0724a1 | 151 | |
2ad9ef06 RL |
152 | thread_scheme => The type of threads is used on the |
153 | configured platform. Currently known | |
154 | values are "(unknown)", "pthreads", | |
155 | "uithreads" (a.k.a solaris threads) and | |
156 | "winthreads". Except for "(unknown)", the | |
157 | actual value is currently ignored but may | |
158 | be used in the future. See further notes | |
159 | below [2]. | |
9e0724a1 RL |
160 | dso_scheme => The type of dynamic shared objects to build |
161 | for. This mostly comes into play with | |
1842f369 | 162 | modules, but can be used for other purposes |
9e0724a1 RL |
163 | as well. Valid values are "DLFCN" |
164 | (dlopen() et al), "DLFCN_NO_H" (for systems | |
165 | that use dlopen() et al but do not have | |
166 | fcntl.h), "DL" (shl_load() et al), "WIN32" | |
167 | and "VMS". | |
e6f98ae4 RL |
168 | asm_arch => The architecture to be used for compiling assembly |
169 | source. This acts as a selector in build.info files. | |
b19fe714 RL |
170 | uplink_arch => The architecture to be used for compiling uplink |
171 | source. This acts as a selector in build.info files. | |
172 | This is separate from asm_arch because it's compiled | |
173 | even when 'no-asm' is given, even though it contains | |
174 | assembler source. | |
a8b2b52f | 175 | perlasm_scheme => The perlasm method used to create the |
9e0724a1 RL |
176 | assembler files used when compiling with |
177 | assembler implementations. | |
178 | shared_target => The shared library building method used. | |
ef2dfc99 RL |
179 | This serves multiple purposes: |
180 | - as index for targets found in shared_info.pl. | |
181 | - as linker script generation selector. | |
182 | To serve both purposes, the index for shared_info.pl | |
183 | should end with '-shared', and this suffix will be | |
184 | removed for use as a linker script generation | |
185 | selector. Note that the latter is only used if | |
186 | 'shared_defflag' is defined. | |
9e0724a1 | 187 | build_scheme => The scheme used to build up a Makefile. |
88087414 RL |
188 | In its simplest form, the value is a string |
189 | with the name of the build scheme. | |
190 | The value may also take the form of a list | |
191 | of strings, if the build_scheme is to have | |
192 | some options. In this case, the first | |
193 | string in the list is the name of the build | |
194 | scheme. | |
45c6e23c | 195 | Currently recognised build scheme is "unified". |
9fe2bb77 RL |
196 | For the "unified" build scheme, this item |
197 | *must* be an array with the first being the | |
198 | word "unified" and the second being a word | |
199 | to identify the platform family. | |
9e0724a1 RL |
200 | |
201 | multilib => On systems that support having multiple | |
202 | implementations of a library (typically a | |
203 | 32-bit and a 64-bit variant), this is used | |
204 | to have the different variants in different | |
205 | directories. | |
206 | ||
1bc563ca AP |
207 | bn_ops => Building options (was just bignum options in |
208 | the earlier history of this option, hence the | |
209 | name). This is a string of words that describe | |
210 | algorithms' implementation parameters that | |
211 | are optimal for the designated target platform, | |
212 | such as the type of integers used to build up | |
213 | the bignum, different ways to implement certain | |
214 | ciphers and so on. To fully comprehend the | |
9e0724a1 RL |
215 | meaning, the best is to read the affected |
216 | source. | |
217 | The valid words are: | |
218 | ||
1bc563ca AP |
219 | THIRTY_TWO_BIT bignum limbs are 32 bits, |
220 | this is default if no | |
221 | option is specified, it | |
222 | works on any supported | |
223 | system [unless "wider" | |
224 | limb size is implied in | |
225 | assembly code]; | |
226 | BN_LLONG bignum limbs are 32 bits, | |
227 | but 64-bit 'unsigned long | |
228 | long' is used internally | |
229 | in calculations; | |
230 | SIXTY_FOUR_BIT_LONG bignum limbs are 64 bits | |
231 | and sizeof(long) is 8; | |
232 | SIXTY_FOUR_BIT bignums limbs are 64 bits, | |
233 | but execution environment | |
234 | is ILP32; | |
235 | RC4_CHAR RC4 key schedule is made | |
236 | up of 'unsigned char's; | |
237 | RC4_INT RC4 key schedule is made | |
238 | up of 'unsigned int's; | |
9e0724a1 RL |
239 | EXPORT_VAR_AS_FN for shared libraries, |
240 | export vars as | |
241 | accessor functions. | |
242 | ||
9fe2bb77 | 243 | padlock_asm_src => Assembler implementation of core parts of |
9e0724a1 RL |
244 | the padlock engine. This is mandatory on |
245 | any platform where the padlock engine might | |
246 | actually be built. | |
247 | ||
248 | ||
249 | [1] as part of the target configuration, one can have a key called | |
250 | 'inherit_from' that indicate what other configurations to inherit | |
251 | data from. These are resolved recursively. | |
252 | ||
b6453a68 | 253 | Inheritance works as a set of default values that can be overridden |
9e0724a1 RL |
254 | by corresponding key values in the inheriting configuration. |
255 | ||
256 | Note 1: any configuration table can be used as a template. | |
257 | Note 2: pure templates have the attribute 'template => 1' and | |
258 | cannot be used as build targets. | |
259 | ||
260 | If several configurations are given in the 'inherit_from' array, | |
261 | the values of same attribute are concatenated with space | |
262 | separation. With this, it's possible to have several smaller | |
263 | templates for different configuration aspects that can be combined | |
264 | into a complete configuration. | |
265 | ||
266 | instead of a scalar value or an array, a value can be a code block | |
267 | of the form 'sub { /* your code here */ }'. This code block will | |
268 | be called with the list of inherited values for that key as | |
269 | arguments. In fact, the concatenation of strings is really done | |
270 | by using 'sub { join(" ",@_) }' on the list of inherited values. | |
271 | ||
272 | An example: | |
273 | ||
274 | "foo" => { | |
275 | template => 1, | |
276 | haha => "ha ha", | |
277 | hoho => "ho", | |
278 | ignored => "This should not appear in the end result", | |
279 | }, | |
280 | "bar" => { | |
281 | template => 1, | |
282 | haha => "ah", | |
283 | hoho => "haho", | |
284 | hehe => "hehe" | |
285 | }, | |
286 | "laughter" => { | |
287 | inherit_from => [ "foo", "bar" ], | |
288 | hehe => sub { join(" ",(@_,"!!!")) }, | |
289 | ignored => "", | |
290 | } | |
291 | ||
292 | The entry for "laughter" will become as follows after processing: | |
293 | ||
294 | "laughter" => { | |
295 | haha => "ha ha ah", | |
296 | hoho => "ho haho", | |
297 | hehe => "hehe !!!", | |
298 | ignored => "" | |
299 | } | |
300 | ||
301 | [2] OpenSSL is built with threading capabilities unless the user | |
2ad9ef06 | 302 | specifies 'no-threads'. The value of the key 'thread_scheme' may |
9e0724a1 RL |
303 | be "(unknown)", in which case the user MUST give some compilation |
304 | flags to Configure. | |
305 | ||
c86ddbe6 RL |
306 | [3] OpenSSL has three types of things to link from object files or |
307 | static libraries: | |
308 | ||
309 | - shared libraries; that would be libcrypto and libssl. | |
310 | - shared objects (sometimes called dynamic libraries); that would | |
1842f369 | 311 | be the modules. |
c86ddbe6 RL |
312 | - applications; those are apps/openssl and all the test apps. |
313 | ||
314 | Very roughly speaking, linking is done like this (words in braces | |
315 | represent the configuration settings documented at the beginning | |
316 | of this file): | |
317 | ||
318 | shared libraries: | |
310f28df RL |
319 | {ld} $(CFLAGS) {lflags} {shared_ldflag} -o libfoo.so \ |
320 | foo/something.o foo/somethingelse.o {ex_libs} | |
c86ddbe6 RL |
321 | |
322 | shared objects: | |
310f28df | 323 | {ld} $(CFLAGS) {lflags} {module_ldflags} -o libeng.so \ |
150624bc | 324 | blah1.o blah2.o -lcrypto {ex_libs} |
c86ddbe6 RL |
325 | |
326 | applications: | |
327 | {ld} $(CFLAGS) {lflags} -o app \ | |
150624bc | 328 | app1.o utils.o -lssl -lcrypto {ex_libs} |
c86ddbe6 | 329 | |
310f28df RL |
330 | [4] There are variants of these attribute, prefixed with `lib_', |
331 | `dso_' or `bin_'. Those variants replace the unprefixed attribute | |
332 | when building library, DSO or program modules specifically. | |
9e0724a1 RL |
333 | |
334 | Historically, the target configurations came in form of a string with | |
df71f0b8 RL |
335 | values separated by colons. This use is deprecated. The string form |
336 | looked like this: | |
9e0724a1 | 337 | |
f0bd4686 | 338 | "target" => "{cc}:{cflags}:{unistd}:{thread_cflag}:{sys_id}:{lflags}:{bn_ops}:{cpuid_obj}:{bn_obj}:{ec_obj}:{des_obj}:{aes_obj}:{bf_obj}:{md5_obj}:{sha1_obj}:{cast_obj}:{rc4_obj}:{rmd160_obj}:{rc5_obj}:{wp_obj}:{cmll_obj}:{modes_obj}:{padlock_obj}:{perlasm_scheme}:{dso_scheme}:{shared_target}:{shared_cflag}:{shared_ldflag}:{shared_extension}:{ranlib}:{arflags}:{multilib}" |
9fe2bb77 RL |
339 | |
340 | ||
341 | Build info files | |
342 | ================ | |
343 | ||
344 | The build.info files that are spread over the source tree contain the | |
345 | minimum information needed to build and distribute OpenSSL. It uses a | |
346 | simple and yet fairly powerful language to determine what needs to be | |
347 | built, from what sources, and other relationships between files. | |
348 | ||
349 | For every build.info file, all file references are relative to the | |
350 | directory of the build.info file for source files, and the | |
351 | corresponding build directory for built files if the build tree | |
352 | differs from the source tree. | |
353 | ||
354 | When processed, every line is processed with the perl module | |
355 | Text::Template, using the delimiters "{-" and "-}". The hashes | |
356 | %config and %target are passed to the perl fragments, along with | |
357 | $sourcedir and $builddir, which are the locations of the source | |
358 | directory for the current build.info file and the corresponding build | |
359 | directory, all relative to the top of the build tree. | |
360 | ||
7f73eafe RL |
361 | 'Configure' only knows inherently about the top build.info file. For |
362 | any other directory that has one, further directories to look into | |
363 | must be indicated like this: | |
364 | ||
365 | SUBDIRS=something someelse | |
366 | ||
367 | On to things to be built; they are declared by setting specific | |
9fe2bb77 RL |
368 | variables: |
369 | ||
370 | PROGRAMS=foo bar | |
371 | LIBS=libsomething | |
1842f369 | 372 | MODULES=libeng |
9fe2bb77 | 373 | SCRIPTS=myhack |
9fe2bb77 | 374 | |
1842f369 | 375 | Note that the files mentioned for PROGRAMS, LIBS and MODULES *must* be |
9fe2bb77 RL |
376 | without extensions. The build file templates will figure them out. |
377 | ||
378 | For each thing to be built, it is then possible to say what sources | |
379 | they are built from: | |
380 | ||
381 | PROGRAMS=foo bar | |
382 | SOURCE[foo]=foo.c common.c | |
383 | SOURCE[bar]=bar.c extra.c common.c | |
384 | ||
385 | It's also possible to tell some other dependencies: | |
386 | ||
387 | DEPEND[foo]=libsomething | |
388 | DEPEND[libbar]=libsomethingelse | |
389 | ||
390 | (it could be argued that 'libsomething' and 'libsomethingelse' are | |
391 | source as well. However, the files given through SOURCE are expected | |
392 | to be located in the source tree while files given through DEPEND are | |
393 | expected to be located in the build tree) | |
394 | ||
46f4e1be | 395 | It's also possible to depend on static libraries explicitly: |
473a9547 RL |
396 | |
397 | DEPEND[foo]=libsomething.a | |
398 | DEPEND[libbar]=libsomethingelse.a | |
399 | ||
400 | This should be rarely used, and care should be taken to make sure it's | |
401 | only used when supported. For example, native Windows build doesn't | |
a8b2b52f | 402 | support building static libraries and DLLs at the same time, so using |
473a9547 RL |
403 | static libraries on Windows can only be done when configured |
404 | 'no-shared'. | |
405 | ||
2a08d1a0 RL |
406 | In some cases, it's desirable to include some source files in the |
407 | shared form of a library only: | |
408 | ||
409 | SHARED_SOURCE[libfoo]=dllmain.c | |
410 | ||
9fe2bb77 RL |
411 | For any file to be built, it's also possible to tell what extra |
412 | include paths the build of their source files should use: | |
413 | ||
414 | INCLUDE[foo]=include | |
415 | ||
b96ab5e6 RL |
416 | It's also possible to specify C macros that should be defined: |
417 | ||
418 | DEFINE[foo]=FOO BAR=1 | |
419 | ||
ae4c7450 RL |
420 | In some cases, one might want to generate some source files from |
421 | others, that's done as follows: | |
422 | ||
423 | GENERATE[foo.s]=asm/something.pl $(CFLAGS) | |
424 | GENERATE[bar.s]=asm/bar.S | |
425 | ||
426 | The value of each GENERATE line is a command line or part of it. | |
436ad81f DB |
427 | Configure places no rules on the command line, except that the first |
428 | item must be the generator file. It is, however, entirely up to the | |
ae4c7450 RL |
429 | build file template to define exactly how those command lines should |
430 | be handled, how the output is captured and so on. | |
431 | ||
2036fd50 RL |
432 | Sometimes, the generator file itself depends on other files, for |
433 | example if it is a perl script that depends on other perl modules. | |
434 | This can be expressed using DEPEND like this: | |
435 | ||
436 | DEPEND[asm/something.pl]=../perlasm/Foo.pm | |
437 | ||
438 | There may also be cases where the exact file isn't easily specified, | |
439 | but an inclusion directory still needs to be specified. INCLUDE can | |
440 | be used in that case: | |
441 | ||
442 | INCLUDE[asm/something.pl]=../perlasm | |
443 | ||
ae4c7450 RL |
444 | NOTE: GENERATE lines are limited to one command only per GENERATE. |
445 | ||
9fe2bb77 RL |
446 | Finally, you can have some simple conditional use of the build.info |
447 | information, looking like this: | |
448 | ||
449 | IF[1] | |
450 | something | |
451 | ELSIF[2] | |
452 | something other | |
453 | ELSE | |
454 | something else | |
455 | ENDIF | |
456 | ||
457 | The expression in square brackets is interpreted as a string in perl, | |
458 | and will be seen as true if perl thinks it is, otherwise false. For | |
459 | example, the above would have "something" used, since 1 is true. | |
460 | ||
461 | Together with the use of Text::Template, this can be used as | |
462 | conditions based on something in the passed variables, for example: | |
463 | ||
84af1bae | 464 | IF[{- $disabled{shared} -}] |
9fe2bb77 RL |
465 | LIBS=libcrypto |
466 | SOURCE[libcrypto]=... | |
467 | ELSE | |
468 | LIBS=libfoo | |
469 | SOURCE[libfoo]=... | |
470 | ENDIF | |
471 | ||
ddf1847d RL |
472 | |
473 | Build-file programming with the "unified" build system | |
474 | ====================================================== | |
475 | ||
476 | "Build files" are called "Makefile" on Unix-like operating systems, | |
477 | "descrip.mms" for MMS on VMS, "makefile" for nmake on Windows, etc. | |
478 | ||
479 | To use the "unified" build system, the target configuration needs to | |
480 | set the three items 'build_scheme', 'build_file' and 'build_command'. | |
481 | In the rest of this section, we will assume that 'build_scheme' is set | |
482 | to "unified" (see the configurations documentation above for the | |
483 | details). | |
484 | ||
485 | For any name given by 'build_file', the "unified" system expects a | |
486 | template file in Configurations/ named like the build file, with | |
487 | ".tmpl" appended, or in case of possible ambiguity, a combination of | |
488 | the second 'build_scheme' list item and the 'build_file' name. For | |
489 | example, if 'build_file' is set to "Makefile", the template could be | |
490 | Configurations/Makefile.tmpl or Configurations/unix-Makefile.tmpl. | |
491 | In case both Configurations/unix-Makefile.tmpl and | |
492 | Configurations/Makefile.tmpl are present, the former takes | |
493 | precedence. | |
494 | ||
495 | The build-file template is processed with the perl module | |
496 | Text::Template, using "{-" and "-}" as delimiters that enclose the | |
497 | perl code fragments that generate configuration-dependent content. | |
498 | Those perl fragments have access to all the hash variables from | |
499 | configdata.pem. | |
500 | ||
501 | The build-file template is expected to define at least the following | |
502 | perl functions in a perl code fragment enclosed with "{-" and "-}". | |
503 | They are all expected to return a string with the lines they produce. | |
504 | ||
ae4c7450 RL |
505 | generatesrc - function that produces build file lines to generate |
506 | a source file from some input. | |
507 | ||
508 | It's called like this: | |
509 | ||
510 | generatesrc(src => "PATH/TO/tobegenerated", | |
511 | generator => [ "generatingfile", ... ] | |
2036fd50 RL |
512 | generator_incs => [ "INCL/PATH", ... ] |
513 | generator_deps => [ "dep1", ... ] | |
e38bd948 RL |
514 | generator => [ "generatingfile", ... ] |
515 | incs => [ "INCL/PATH", ... ], | |
ae4c7450 RL |
516 | deps => [ "dep1", ... ], |
517 | intent => one of "libs", "dso", "bin" ); | |
518 | ||
519 | 'src' has the name of the file to be generated. | |
520 | 'generator' is the command or part of command to | |
521 | generate the file, of which the first item is | |
522 | expected to be the file to generate from. | |
523 | generatesrc() is expected to analyse and figure out | |
524 | exactly how to apply that file and how to capture | |
2036fd50 RL |
525 | the result. 'generator_incs' and 'generator_deps' |
526 | are include directories and files that the generator | |
527 | file itself depends on. 'incs' and 'deps' are | |
528 | include directories and files that are used if $(CC) | |
529 | is used as an intermediary step when generating the | |
530 | end product (the file indicated by 'src'). 'intent' | |
531 | indicates what the generated file is going to be | |
532 | used for. | |
ae4c7450 | 533 | |
ddf1847d RL |
534 | src2obj - function that produces build file lines to build an |
535 | object file from source files and associated data. | |
536 | ||
537 | It's called like this: | |
538 | ||
539 | src2obj(obj => "PATH/TO/objectfile", | |
540 | srcs => [ "PATH/TO/sourcefile", ... ], | |
541 | deps => [ "dep1", ... ], | |
45502bfe RL |
542 | incs => [ "INCL/PATH", ... ] |
543 | intent => one of "lib", "dso", "bin" ); | |
ddf1847d | 544 | |
aa343982 RL |
545 | 'obj' has the intended object file with '.o' |
546 | extension, src2obj() is expected to change it to | |
547 | something more suitable for the platform. | |
ddf1847d RL |
548 | 'srcs' has the list of source files to build the |
549 | object file, with the first item being the source | |
550 | file that directly corresponds to the object file. | |
50e83cdd | 551 | 'deps' is a list of explicit dependencies. 'incs' |
45502bfe RL |
552 | is a list of include file directories. Finally, |
553 | 'intent' indicates what this object file is going | |
554 | to be used for. | |
ddf1847d RL |
555 | |
556 | obj2lib - function that produces build file lines to build a | |
557 | static library file ("libfoo.a" in Unix terms) from | |
558 | object files. | |
559 | ||
560 | called like this: | |
561 | ||
562 | obj2lib(lib => "PATH/TO/libfile", | |
563 | objs => [ "PATH/TO/objectfile", ... ]); | |
564 | ||
565 | 'lib' has the intended library file name *without* | |
566 | extension, obj2lib is expected to add that. 'objs' | |
aa343982 | 567 | has the list of object files to build this library. |
ddf1847d | 568 | |
aa343982 RL |
569 | libobj2shlib - backward compatibility function that's used the |
570 | same way as obj2shlib (described next), and was | |
571 | expected to build the shared library from the | |
572 | corresponding static library when that was suitable. | |
573 | NOTE: building a shared library from a static | |
574 | library is now DEPRECATED, as they no longer share | |
575 | object files. Attempting to do this will fail. | |
576 | ||
577 | obj2shlib - function that produces build file lines to build a | |
ddf1847d | 578 | shareable object library file ("libfoo.so" in Unix |
aa343982 | 579 | terms) from the corresponding object files. |
ddf1847d RL |
580 | |
581 | called like this: | |
582 | ||
aa343982 RL |
583 | obj2shlib(shlib => "PATH/TO/shlibfile", |
584 | lib => "PATH/TO/libfile", | |
585 | objs => [ "PATH/TO/objectfile", ... ], | |
586 | deps => [ "PATH/TO/otherlibfile", ... ]); | |
ddf1847d | 587 | |
aa343982 RL |
588 | 'lib' has the base (static) library ffile name |
589 | *without* extension. This is useful in case | |
590 | supporting files are needed (such as import | |
591 | libraries on Windows). | |
b6453a68 | 592 | 'shlib' has the corresponding shared library name |
ddf1847d RL |
593 | *without* extension. 'deps' has the list of other |
594 | libraries (also *without* extension) this library | |
595 | needs to be linked with. 'objs' has the list of | |
aa343982 | 596 | object files to build this library. |
ddf1847d | 597 | |
5386287c RL |
598 | obj2dso - function that produces build file lines to build a |
599 | dynamic shared object file from object files. | |
ddf1847d RL |
600 | |
601 | called like this: | |
602 | ||
5386287c RL |
603 | obj2dso(lib => "PATH/TO/libfile", |
604 | objs => [ "PATH/TO/objectfile", ... ], | |
605 | deps => [ "PATH/TO/otherlibfile", | |
606 | ... ]); | |
ddf1847d | 607 | |
aa343982 | 608 | This is almost the same as obj2shlib, but the |
ddf1847d | 609 | intent is to build a shareable library that can be |
aa343982 | 610 | loaded in runtime (a "plugin"...). |
ddf1847d RL |
611 | |
612 | obj2bin - function that produces build file lines to build an | |
613 | executable file from object files. | |
614 | ||
615 | called like this: | |
616 | ||
617 | obj2bin(bin => "PATH/TO/binfile", | |
618 | objs => [ "PATH/TO/objectfile", ... ], | |
619 | deps => [ "PATH/TO/libfile", ... ]); | |
620 | ||
621 | 'bin' has the intended executable file name | |
622 | *without* extension, obj2bin is expected to add | |
aa343982 RL |
623 | that. 'objs' has the list of object files to build |
624 | this library. 'deps' has the list of library files | |
625 | (also *without* extension) that the programs needs | |
626 | to be linked with. | |
ddf1847d RL |
627 | |
628 | in2script - function that produces build file lines to build a | |
629 | script file from some input. | |
630 | ||
631 | called like this: | |
632 | ||
633 | in2script(script => "PATH/TO/scriptfile", | |
634 | sources => [ "PATH/TO/infile", ... ]); | |
635 | ||
636 | 'script' has the intended script file name. | |
637 | 'sources' has the list of source files to build the | |
638 | resulting script from. | |
639 | ||
640 | In all cases, file file paths are relative to the build tree top, and | |
641 | the build file actions run with the build tree top as current working | |
642 | directory. | |
643 | ||
644 | Make sure to end the section with these functions with a string that | |
b6453a68 | 645 | you thing is appropriate for the resulting build file. If nothing |
ddf1847d RL |
646 | else, end it like this: |
647 | ||
648 | ""; # Make sure no lingering values end up in the Makefile | |
649 | -} | |
44eb65ce RL |
650 | |
651 | ||
652 | Configure helper scripts | |
653 | ======================== | |
654 | ||
655 | Configure uses helper scripts in this directory: | |
656 | ||
657 | Checker scripts | |
658 | --------------- | |
659 | ||
660 | These scripts are per platform family, to check the integrity of the | |
661 | tools used for configuration and building. The checker script used is | |
662 | either {build_platform}-{build_file}-checker.pm or | |
663 | {build_platform}-checker.pm, where {build_platform} is the second | |
664 | 'build_scheme' list element from the configuration target data, and | |
665 | {build_file} is 'build_file' from the same target data. | |
666 | ||
667 | If the check succeeds, the script is expected to end with a non-zero | |
668 | expression. If the check fails, the script can end with a zero, or | |
669 | with a `die`. |