Skip to content
  1. Jan 08, 2018
  2. Jan 04, 2018
  3. Jan 02, 2018
  4. Dec 28, 2017
  5. Dec 27, 2017
  6. Dec 18, 2017
  7. Dec 15, 2017
  8. Dec 12, 2017
  9. Dec 07, 2017
  10. 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
  11. Nov 13, 2017
  12. Nov 12, 2017
  13. Nov 10, 2017
  14. Nov 08, 2017
  15. Oct 31, 2017
  16. Oct 13, 2017
  17. Oct 09, 2017
  18. Oct 04, 2017
  19. Sep 21, 2017
  20. Aug 25, 2017
  21. Aug 18, 2017
  22. Aug 17, 2017
  23. Aug 16, 2017
  24. Aug 15, 2017
  25. Jul 26, 2017
    • Richard Levitte's avatar
      Simplify the handling of shared library version numbers · d4453024
      Richard Levitte authored
      
      
      $(SHLIB_MAJOR).$(SHLIB_MINOR) is really a synonym for
      $(SHLIB_VERSION_NUMBER), and is therefore an added complexity,
      so better to use $(SHLIB_VERSION_NUMBER) directly.  SHLIB_MAJOR and
      SHLIB_MINOR are now unused, but are kept around purely as information
      in case someone relies on their existence.
      
      At the same time, add support for custom shared library extensions
      with the three new Makefile variables SHLIB_EXT, SHLIB_EXT_SIMPLE and
      SHLIB_EXT_IMPORT.  By default, they hold the variants of shared
      library extensions we support.  On mingw and cygwin, SHLIB_EXT_IMPORT
      is defined; on all other Unix platforms, it's empty.
      
      An example to get shared libraries with a slightly different SOVER name:
      
          $ make SHLIB_EXT='.$(SHLIB_VERSION_NUMBER).so'
      
      Fixes #3902
      
      Reviewed-by: default avatarAndy Polyakov <appro@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/3964)
      d4453024
  26. Jul 24, 2017
    • Richard Levitte's avatar
      Simplify Makefile.shared · d07abe13
      Richard Levitte authored
      
      
      Makefile.shared was designed to figure out static library names,
      shared library names, library version compatibility, import library
      names and the like on its own.  This was a design for pre-1.1.0
      OpenSSL because the main Makefile didn't have all that knowledge.
      
      With 1.1.0, the situation isn't the same, a lot more knowledge is
      included in the main Makefile, and while Makefile.shared did things
      right most of the time (there are some corner cases, such as the
      choice of .sl or .so as DSO extension on some HPUX versions), there's
      still an inherent fragility when one has to keep an eye on
      Makefile.shared to make sure it produces what the main Makefile
      produces.
      
      This change simplifies Makefile.shared by removing all its
      "intelligence" and have it depend entirely on the input from the main
      Makefile instead.  That way, all the naming is driven from
      configuration data.
      
      Reviewed-by: default avatarRich Salz <rsalz@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/3983)
      d07abe13
  27. Jul 07, 2017
  28. Jul 01, 2017
  29. Jun 30, 2017
  30. Jun 28, 2017
  31. Jun 21, 2017
  32. Jun 16, 2017