X-Git-Url: https://git.openssl.org/gitweb/?p=openssl.git;a=blobdiff_plain;f=Configurations%2FREADME.design;h=574982fb5a2bdb4aff80dfc8c94403ca1e0aaae1;hp=8b94e220e30306918ac18a7f0986450d2b414943;hb=2a08d1a05db937f8b1a62422b78ffe2fa07d3ead;hpb=b6453a68bbb34c901a2eaf24012d0a3afcbf52ff diff --git a/Configurations/README.design b/Configurations/README.design index 8b94e220e3..574982fb5a 100644 --- a/Configurations/README.design +++ b/Configurations/README.design @@ -89,11 +89,8 @@ depends on the library 'libssl' to function properly. SOURCE[../libcrypto]=aes.c evp.c cversion.c DEPEND[cversion.o]=buildinf.h - BEGINRAW[Makefile(unix)] - crypto/buildinf.h : Makefile - perl util/mkbuildinf.h "$(CC) $(CFLAGS)" "$(PLATFORM)" \ - > crypto/buildinf.h - ENDRAW[Makefile(unix)] + GENERATE[buildinf.h]=../util/mkbuildinf.pl "$(CC) $(CFLAGS)" "$(PLATFORM)" + DEPEND[buildinf.h]=../Makefile This is the build.info file in 'crypto', and it tells us a little more about what's needed to produce 'libcrypto'. LIBS is used again to @@ -161,11 +158,8 @@ information comes down to this: DEPEND[engines/libossltest]=libcrypto INCLUDE[engines/libossltest]=include - BEGINRAW[Makefile(unix)] - crypto/buildinf.h : Makefile - perl util/mkbuildinf.h "$(CC) $(CFLAGS)" "$(PLATFORM)" \ - > crypto/buildinf.h - ENDRAW[Makefile(unix)] + GENERATE[crypto/buildinf.h]=util/mkbuildinf.pl "$(CC) $(CFLAGS)" "$(PLATFORM)" + DEPEND[crypto/buildinf.h]=Makefile A few notes worth mentioning: @@ -180,7 +174,7 @@ The indexes for SOURCE, INCLUDE and ORDINALS must only be end product files, such as libraries, programs or engines. The values of SOURCE variables must only be source files (possibly generated) -DEPEND shows a relationship between different end product files, such +DEPEND shows a relationship between different produced files, such as a program depending on a library, or between an object file and some extra source file. @@ -239,6 +233,10 @@ indexes: SOURCE variables, and AS source files for programs and libraries. + shared_sources => + a hash table just like 'sources', but only as source + files (object files) for building shared libraries. + As an example, here is how the build.info files example from the section above would be digested into a %unified_info table: @@ -296,12 +294,12 @@ section above would be digested into a %unified_info table: "libcrypto" => [ "crypto", - "util/libeay.num", + "util/libcrypto.num", ], "libssl" => [ "ssl", - "util/ssleay.num", + "util/libssl.num", ], }, "programs" => @@ -442,7 +440,7 @@ etc. this library. 'ordinals' MAY be present, and when it is, its value is an array where the word is "crypto" or "ssl" and the file is one of the ordinal - files util/libeay.num or util/ssleay.num in the + files util/libcrypto.num or util/libssl.num in the source directory. This function has a choice; it can use the @@ -515,7 +513,7 @@ following calls: lib => "libssl", objs => [ "ssl/tls.o" ], deps => [ "libcrypto" ] - ordinals => [ "ssl", "util/ssleay.num" ]); + ordinals => [ "ssl", "util/libssl.num" ]); obj2lib(lib => "libssl" objs => [ "ssl/tls.o" ]);