Skip to content
  1. Jan 31, 2018
  2. Jan 30, 2018
  3. Jan 29, 2018
  4. Jan 28, 2018
  5. Jan 24, 2018
    • Richard Levitte's avatar
      Configure: let INCLUDEs set on binaries "trickle down" to the objects · 1b5ad51f
      Richard Levitte authored
      
      
      This ensures that only one set of includes is associated with each
      object file, reagardless of where it's used.
      
      For example, if apps/build.info has this:
      
          SOURCE[openssl]=foo.c
          INCLUDE[openssl]=.. ../include
      
      and test/build.info has this:
      
          SOURCE[footest]=../apps/foo.c
          INCLUDE[footest]=../include
      
      The inclusion directories used for apps/foo.o would differ depending
      on which program's dependencies get generated first in the build file.
      
      With this change, all those INCLUDEs get combined into one set of
      inclusion directories tied to the object file.
      
      Reviewed-by: default avatarRich Salz <rsalz@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/5153)
      1b5ad51f
  6. Jan 23, 2018
  7. Jan 22, 2018
  8. Jan 19, 2018
  9. Jan 15, 2018
  10. Jan 09, 2018
  11. Jan 08, 2018
  12. Jan 04, 2018
  13. Jan 02, 2018
  14. Dec 28, 2017
  15. Dec 27, 2017
  16. Dec 18, 2017
  17. Dec 15, 2017
  18. Dec 12, 2017
  19. Dec 07, 2017
  20. Nov 30, 2017
    • Viktor Dukhovni's avatar
      Make possible variant SONAMEs and symbol versions · 822b5e26
      Viktor Dukhovni authored
      
      
      This small change in the Unix template and shared library build
      scripts enables building "variant" shared libraries.  A "variant"
      shared library has a non-default SONAME, and non default symbol
      versions.  This makes it possible to build (say) an OpenSSL 1.1.0
      library that can coexist without conflict in the same process address
      space as the system's default OpenSSL library which may be OpenSSL
      1.0.2.
      
      Such "variant" shared libraries make it possible to link applications
      against a custom OpenSSL library installed in /opt/openssl/1.1 or
      similar location, and not risk conflict with an indirectly loaded
      OpenSSL runtime that is required by some other dependency.
      
      Variant shared libraries have been fully tested under Linux, and
      build successfully on MacOS/X producing variant DYLD names.  MacOS/X
      Darwin has no symbol versioning, but has a non-flat library namespace.
      Variant libraries may therefore support multiple OpenSSL libraries
      in the same address space also with MacOS/X, despite lack of symbol
      versions, but this has not been verified.
      
      Variant shared libraries are optional and off by default.
      
      Reviewed-by: default avatarRichard Levitte <levitte@openssl.org>
      822b5e26
  21. Nov 13, 2017
  22. Nov 12, 2017
  23. Nov 10, 2017
  24. Nov 08, 2017