aboutsummaryrefslogtreecommitdiff
path: root/crypto/txt_db
diff options
context:
space:
mode:
authorRichard Levitte <levitte@openssl.org>2016-01-29 19:45:51 +0100
committerRichard Levitte <levitte@openssl.org>2016-02-01 12:46:58 +0100
commit9fe2bb77c40f5fd3624b30f1b0c3cd8b791ca615 (patch)
tree466c23f4fe9dd83bfcf218bde29500c5aa2c0b55 /crypto/txt_db
parent1d852772355105cdb1cb0e7451b28358dd475e04 (diff)
downloadopenssl-9fe2bb77c40f5fd3624b30f1b0c3cd8b791ca615.zip
openssl-9fe2bb77c40f5fd3624b30f1b0c3cd8b791ca615.tar.gz
openssl-9fe2bb77c40f5fd3624b30f1b0c3cd8b791ca615.tar.bz2
unified build scheme: a first introduction
The "unified" build scheme revolves around small information files, build.info, which each describe their own bit of everything that needs to be built, using a mini-language described in Configurations/README. The information in build.info file contain references to source files and final result. Object files are not mentioned at all, they are simply from source files. Because of this, all the *_obj items in Configurations/*.conf are renamed to *_asm_src and the files listed in the values are change from object files to their corresponding source files. For the sake of the other build schemes, Configure generates corresponding *_obj entries in %target. Furthermore, the "unified" build scheme supports having a build directory tree separate from the source directry tree. All paths in a build.info file is assumed to be relative to its location, either within the source tree or within the build tree. Reviewed-by: Andy Polyakov <appro@openssl.org>
Diffstat (limited to 'crypto/txt_db')
0 files changed, 0 insertions, 0 deletions