1. 11 3月, 2016 2 次提交
  2. 10 3月, 2016 2 次提交
  3. 09 3月, 2016 6 次提交
  4. 08 3月, 2016 5 次提交
  5. 07 3月, 2016 3 次提交
  6. 05 3月, 2016 2 次提交
  7. 04 3月, 2016 2 次提交
  8. 03 3月, 2016 7 次提交
    • R
      Don't copy from %target to %config so much, see %config as a complement · 2952b9b8
      Richard Levitte 提交于
      We copied $target{cflags}, $target{defines} and a few more to %config,
      just to add to the entries.  Avoid doing so, and let the build templates
      deal with combining the two.
      
      There are a few cases where we still fiddle with %target, but that's
      acceptable.
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      2952b9b8
    • R
      Configure - Get rid of the special thread_cflag, replace with thread_scheme · 9c62a279
      Richard Levitte 提交于
      The thread_cflag setting filled a double role, as kinda sorta an
      indicator of thread scheme, and as cflags.  Some configs also added
      lflags and ex_libs for multithreading regardless of if threading would
      be enabled or not.
      
      Instead of this, add threading cflags among in the cflag setting,
      threading lflags in the lflag setting and so on if and only if threads
      are enabled (which they are by default).
      
      Also, for configs where there are no special cflags for threading (the
      VMS configs are of that kind), this makes it possible to still clearly
      mention what thread scheme is used.
      
      The exact value of thread scheme is currently ignored except when it's
      "(unknown)", and thereby only serves as a flag to tell if we know how
      to build for multi-threading in a particular config.  Yet, the
      currently used values are "(unknown)", "pthreads", "uithreads" (a.k.a
      solaris threads) and "winthreads".
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      9c62a279
    • R
      Configure - get rid of the special debug_ and release_ settings · 8864f0de
      Richard Levitte 提交于
      Instead, make the build type ("debug" or "release") available through
      $config{build_type} and let the configs themselves figure out what the
      usual settings (such as "cflags", "lflags" and so on) should be
      accordingly.
      
      The benefit with this is that we can now have debug and release
      variants of any setting, not just those Configure supports, and may
      also involve other factors (the MSVC flags /MD[d] and /MT[d] involve
      both build type and whether threading is enabled or not)
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      8864f0de
    • R
      Minimize copied config settings · 940a09ba
      Richard Levitte 提交于
      $target{lflags} and $target{plib_flag} were copied to %config for no
      good reason.
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      940a09ba
    • R
      Configure - move the addition of the zlib / libz lib to configs · 98fdbce0
      Richard Levitte 提交于
      Configure had the Unix centric addition of -lz when linking with zlib
      is enabled, which doesn't work on other platforms.  Therefore, we move
      it to the BASE_unix config template and add corresponding ones in the
      other BASE_* config templates.  The Windows one is probably incomplete,
      but that doesn't matter for the moment, as mk1mf does it's own thing
      anyway.
      
      This required making the %withargs table global, so perl snippets in
      the configs can use it.
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      98fdbce0
    • R
      Configure - Rename BASE to DEFAULTS and add a few inheritable BASEs · d2b2221a
      Richard Levitte 提交于
      These BASE templates are intended to hold values that are common for
      all configuration variants for whole families of configurations.
      
      So far, three "families" are identified: Unix, Windows and VMS, mostly
      characterised by the build system they currently use.
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      d2b2221a
    • R
      Configure - Allow CODErefs and ARRAYrefs in configuration setting arrays · b0b92a5b
      Richard Levitte 提交于
      This provides for more powerful lazy evaluation and buildup of the
      setting contents.  For example, something like this becomes possible:
      
          defines => [ sub { $config{thisorthat} ? "FOO" : () } ]
      
      Any undefined result of such functions (such as 'undef' or the empty
      list) will be ignored.
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      b0b92a5b
  9. 02 3月, 2016 2 次提交
  10. 01 3月, 2016 1 次提交
  11. 28 2月, 2016 1 次提交
  12. 27 2月, 2016 2 次提交
  13. 26 2月, 2016 2 次提交
  14. 23 2月, 2016 3 次提交