1. 18 9月, 2016 1 次提交
  2. 16 9月, 2016 3 次提交
  3. 15 9月, 2016 2 次提交
  4. 13 9月, 2016 1 次提交
  5. 12 9月, 2016 1 次提交
  6. 09 9月, 2016 2 次提交
  7. 08 9月, 2016 2 次提交
  8. 05 9月, 2016 1 次提交
    • R
      Unix build: have the makedepend and cc actions in one recipe · 7e5b8b93
      Richard Levitte 提交于
      In the case of using an independent makedepend, we had split that into
      two separate recipes, one depending on the other.  However, there are
      cases where the makedepend recipe was always trying, but doesn't
      update the time stamp of the .d file because there are no actual
      changes, and thereby causing constant updates of the object files.
      
      This change makes one recipe that takes care of both makedepend och
      cc, thereby avoiding these extra updates.
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      7e5b8b93
  9. 02 9月, 2016 5 次提交
  10. 01 9月, 2016 1 次提交
  11. 30 8月, 2016 1 次提交
  12. 27 8月, 2016 1 次提交
  13. 25 8月, 2016 1 次提交
  14. 22 8月, 2016 1 次提交
    • R
      VMS: Use strict refdef extern model when building library object files · 68a39960
      Richard Levitte 提交于
      Most of the time, this isn't strictly needed.  However, in the default
      extern model (called relaxed refdef), symbols are treated as weak
      common objects unless they are initialised.  The librarian doesn't
      include weak symbols in the (static) libraries, which renders them
      invisible when linking a program with said those libraries, which is a
      problem at times.
      
      Using the strict refdef model is much more like standard C on all
      other platforms, and thereby avoid the issues that come with the
      relaxed refdef model.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      68a39960
  15. 06 8月, 2016 1 次提交
  16. 05 8月, 2016 2 次提交
  17. 03 8月, 2016 1 次提交
  18. 02 8月, 2016 2 次提交
  19. 01 8月, 2016 2 次提交
  20. 31 7月, 2016 1 次提交
  21. 27 7月, 2016 1 次提交
  22. 22 7月, 2016 1 次提交
  23. 20 7月, 2016 2 次提交
  24. 19 7月, 2016 3 次提交
  25. 15 7月, 2016 1 次提交
    • R
      Windows: allow input and output flags to end with a space, or not · 1fc431ba
      Richard Levitte 提交于
      With a number of tools, especially those coming with Visual Studio,
      some command options are separated from their argument with a space,
      others with a space.  Since we parametrise them, we can't know
      beforehand which it will be, so we must allow the input and output
      options to have either.
      
      However, spaces at the end of nmake macro values are trimmed, so allow
      spaces to exist by adding a reference to an undefined macro at the end.
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      1fc431ba