aboutsummaryrefslogtreecommitdiffstats
path: root/Configurations/README.design
Commit message (Collapse)AuthorAgeFilesLines
* Document the enhancements for DEPEND and INCLUDE and use a better exampleRichard Levitte2016-04-251-21/+59
| | | | Reviewed-by: Emilia Käsper <emilia@openssl.org>
* Update the Configurations READMEsRichard Levitte2016-04-221-23/+57
| | | | Reviewed-by: Tim Hudson <tjh@openssl.org>
* Make it possible to specify source files that will only be used for shared libsRichard Levitte2016-03-301-0/+4
| | | | | | | | | | There are rare cases when an object file will only be used when building a shared library. To enable this, we introduce SHARED_SOURCE: SHARED_SOURCE[libfoo]=dllmain.c Reviewed-by: Andy Polyakov <appro@openssl.org>
* Unified - Add the build.info command GENERATE, to generate source filesRichard Levitte2016-03-071-11/+5
| | | | | | | | | | | | | | | | In some cases, one might want to generate some source files from others, that's done as follows: GENERATE[foo.s]=asm/something.pl $(CFLAGS) GENERATE[bar.s]=asm/bar.S The value of each GENERATE line is a command line or part of it. Configure places no rules on the command line, except the the first item muct be the generator file. It is, however, entirely up to the build file template to define exactly how those command lines should be handled, how the output is captured and so on. Reviewed-by: Rich Salz <rsalz@openssl.org>
* Change names of ordinals and libs, libeay => libcrypto and ssleay => libsslRichard Levitte2016-03-051-4/+4
| | | | Reviewed-by: Rich Salz <rsalz@openssl.org>
* GH753: More spelling fixFdaSilvaYY2016-02-271-6/+6
| | | | | Signed-off-by: Rich Salz <rsalz@akamai.com> Reviewed-by: Kurt Roeckx <kurt@openssl.org>
* Always build library object files with shared library cflagsRichard Levitte2016-02-201-3/+6
| | | | | | | | | | | | | | | | This takes us away from the idea that we know exactly how our static libraries are going to get used. Instead, we make them available to build shareable things with, be it other shared libraries or DSOs. On the other hand, we also have greater control of when the shared library cflags. They will never be used with object files meant got binaries, such as apps/openssl or test/test*. With unified, we take this a bit further and prepare for having to deal with extra cflags specifically to be used with DSOs (dynamic engines), libraries and binaries (applications). Reviewed-by: Rich Salz <rsalz@openssl.org>
* Don't treat .d (depend) files separately from object filesRichard Levitte2016-02-181-18/+0
| | | | | | | | | | | | | .d (.MMS in the VMS world) files with just dependencies are built from exactly the same conditions as the object files. Therefore, the rules for them can be built at the same time as the rules for the corresponding object files. This removes the requirement for a src2dep function in the build file templates, and for common.tmpl to call it. In the end, the existence of depend files is entirely up to the build file. Reviewed-by: Rich Salz <rsalz@openssl.org>
* unified build scheme: add a design documentRichard Levitte2016-02-091-0/+550
This documents describes the three steps from build.info files via the %unified_info database to the build-file templates, along with some examples showing how the data gets processed along the way. Reviewed-by: Viktor Dukhovni <viktor@openssl.org>