1. 08 2月, 2016 1 次提交
  2. 07 2月, 2016 1 次提交
  3. 06 2月, 2016 4 次提交
  4. 05 2月, 2016 2 次提交
  5. 04 2月, 2016 8 次提交
  6. 03 2月, 2016 1 次提交
  7. 01 2月, 2016 2 次提交
  8. 31 1月, 2016 1 次提交
  9. 30 1月, 2016 3 次提交
  10. 29 1月, 2016 1 次提交
  11. 28 1月, 2016 1 次提交
  12. 26 1月, 2016 5 次提交
  13. 25 1月, 2016 1 次提交
    • R
      Move pqueue into ssl · cf2cede4
      Rich Salz 提交于
      This is an internal facility, never documented, not for
      public consumption.  Move it into ssl (where it's only used
      for DTLS).
      
      I also made the typedef's for pqueue and pitem follow our style: they
      name structures, not pointers.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      cf2cede4
  14. 24 1月, 2016 1 次提交
  15. 23 1月, 2016 4 次提交
    • R
      Refactor file writing - Adapt util/mkdef.pl to use configdata.pm · 3fa04f0d
      Richard Levitte 提交于
      For this adaptation, the variables $options and $version needed to
      move to %config in Configure, and why not move all other variables
      holding diverse version numbers at the same time?
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      3fa04f0d
    • R
    • R
      Refactor file writing - arrange for use of bundled Perl modules as fallback · 35c3a562
      Richard Levitte 提交于
      For our own convenience, we need a mechanism to be able to fall back
      on bundled Perl modules.  It's a minimal package that's called like
      this:
      
          use with_fallback qw(Module1 Module2 ...);
      
      For each module, it will try to require them from the system
      installation, and failing that, it will temporarly add external/perl
      and try to require transfer::{ModuleName}.  It requires that each
      bundled Perl modules is accompanied by a small transfer module
      (external/perl/transfer/ModuleName.pm in our example) that knows
      exactly what to load.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      35c3a562
    • R
      Refactor file writing - introduce template driven file writing · 291e94df
      Richard Levitte 提交于
      apps/CA.pl and tools/c_rehash are built from template files.  So far,
      this was done by Configure, which created its own problems as it
      forced everyone to reconfigure just because one of the template files
      had changed.
      Instead, have those files created as part of the normal build in apps/
      and in tools/.
      
      Furthermore, this prepares for a future where Configure may produce
      entirely other build files than Makefile, and the latter can't be
      guaranteed to be the holder of all information for other scripts.
      Instead, configdata.pm (described below) becomes the center of
      configuration information.
      
      This introduces a few new things:
      
      %config         a hash table to hold all kinds of configuration data
                      that can be used by any other script.
      configdata.pm   a perl module that Configure writes.  It currently
                      holds the hash tables %config and %target.
      util/dofile.pl  a script that takes a template on STDIN and outputs
                      the result after applying configuration data on it.
                      It's supposed to be called like this:
      
                              perl -I$(TOP) -Mconfigdata < template > result
      
                      or
      
                              perl -I$(TOP) -Mconfigdata templ1 templ2 ... > result
      
                      Note: util/dofile.pl requires Text::Template.
      
      As part of this changed, remove a number of variables that are really
      just copies of entries in %target, and use %target directly.  The
      exceptions are $target{cflags} and $target{lflags}, they do get copied
      to $cflags and $lflags.  The reason for this is that those variable
      potentially go through a lot of changes and would rather deserve a
      place in %config.  That, however, is for another commit.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      291e94df
  16. 22 1月, 2016 1 次提交
    • R
      Refresh the thinking of --prefix and --openssldir · d74dfafd
      Richard Levitte 提交于
      --prefix is now exclusively used for software and manual installation.
      --openssldir is not exclusively used as a default location for certs,
      keys and the default openssl.cnf.
      
      This change is made to bring clarity, to have the two less
      intertwined, and to be more compatible with the usual ways of software
      installation.
      
      Please change your habits and scripts to use --prefix rather than
      --openssldir for installation location now.
      Reviewed-by: NViktor Dukhovni <viktor@openssl.org>
      d74dfafd
  17. 20 1月, 2016 1 次提交
  18. 19 1月, 2016 1 次提交
  19. 18 1月, 2016 1 次提交