1. 22 2月, 2016 5 次提交
  2. 20 2月, 2016 2 次提交
    • R
      Build dynamic engines even if configured "no-shared" · 343ec2b0
      Richard Levitte 提交于
      Until now, the engines in engines/ were only built as dynamicaly
      loadable ones if shared libraries were built.
      
      We not dissociate the two and can build dynamicaly loadable engines
      even if we only build static libcrypto and libssl.  This is controlled
      with the option (enable|disable|no)-static-engine, defaulting to
      no-static-engine.
      
      Note that the engines in crypto/engine/ (dynamic and cryptodev) will
      always be built into libcrypto.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      343ec2b0
    • R
      Always build library object files with shared library cflags · 45502bfe
      Richard Levitte 提交于
      This takes us away from the idea that we know exactly how our static
      libraries are going to get used.  Instead, we make them available to
      build shareable things with, be it other shared libraries or DSOs.
      
      On the other hand, we also have greater control of when the shared
      library cflags.  They will never be used with object files meant got
      binaries, such as apps/openssl or test/test*.
      
      With unified, we take this a bit further and prepare for having to
      deal with extra cflags specifically to be used with DSOs (dynamic
      engines), libraries and binaries (applications).
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      45502bfe
  3. 19 2月, 2016 5 次提交
    • R
      Misc small fixes. · f99f91f1
      Richard Levitte 提交于
      Better libclean that removes the exact files that have been built,
      nothing more and nothing less.
      
      Corrected typo
      
      A couple of editorial changes.
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      f99f91f1
    • R
      Let Configure figure out the diverse shared library and DSO extensions · e987f9f2
      Richard Levitte 提交于
      Then it can pass around the information where it belongs.  The
      Makefile templates pick it up along with other target data, the
      DSO module gets to pick up the information through
      crypto/include/internal/dso_conf.h
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      e987f9f2
    • R
      Rethink the uplink / applink story · 3a55c92b
      Richard Levitte 提交于
      Adding uplink and applink to some builds was done by "magic", the
      configuration for "mingw" only had a macro definition, the Configure
      would react to its presence by adding the uplink source files to
      cpuid_asm_src, and crypto/build.info inherited dance to get it
      compiled, and Makefile.shared made sure applink.o would be
      appropriately linked in.  That was a lot under the hood.
      
      To replace this, we create a few template configurations in
      Configurations/00-base-templates.conf, inherit one of them in the
      "mingw" configuration, the rest is just about refering to the
      $target{apps_aux_src} / $target{apps_obj} in the right places.
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      3a55c92b
    • R
      Remove all special make depend flags, as well as OPENSSL_DOING_MAKEDEPEND · ce192ebe
      Richard Levitte 提交于
      All those flags existed because we had all the dependencies versioned
      in the repository, and wanted to have it be consistent, no matter what
      the local configuration was.  Now that the dependencies are gone from
      the versioned Makefile.ins, it makes much more sense to use the exact
      same flags as when compiling the object files.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      ce192ebe
    • R
      Remove outdated DEBUG flags. · d63a5e5e
      Rich Salz 提交于
      Add -DBIO_DEBUG to --strict-warnings.
      Remove comments about outdated debugging ifdef guards.
      Remove md_rand ifdef guarding an assert; it doesn't seem used.
      Remove the conf guards in conf_api since we use OPENSSL_assert, not assert.
      For pkcs12 stuff put OPENSSL_ in front of the macro name.
      Merge TLS_DEBUG into SSL_DEBUG.
      Various things just turned on/off asserts, mainly for checking non-NULL
      arguments, which is now removed: camellia, bn_ctx, crypto/modes.
      Remove some old debug code, that basically just printed things to stderr:
        DEBUG_PRINT_UNKNOWN_CIPHERSUITES, DEBUG_ZLIB, OPENSSL_RI_DEBUG,
        RL_DEBUG, RSA_DEBUG, SCRYPT_DEBUG.
      Remove OPENSSL_SSL_DEBUG_BROKEN_PROTOCOL.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      d63a5e5e
  4. 18 2月, 2016 6 次提交
  5. 17 2月, 2016 1 次提交
  6. 16 2月, 2016 3 次提交
  7. 15 2月, 2016 1 次提交
  8. 14 2月, 2016 1 次提交
  9. 13 2月, 2016 3 次提交
  10. 12 2月, 2016 3 次提交
  11. 11 2月, 2016 5 次提交
  12. 10 2月, 2016 5 次提交
    • R
      unified build scheme: Try to nudge users to try the "unified" build · 242ffb05
      Richard Levitte 提交于
      This commit SHALL be reverted before final release.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      242ffb05
    • R
      Configure et al: move the installation directory logic to Makefiles · 5482dac9
      Richard Levitte 提交于
      The logic to figure out the combinations of --prefix and --openssldir
      has stayed in Configure so far, with Unix paths as defaults.
      
      However, since we're making Configure increasingly platform agnostic,
      these defaults need to change and adapt to the platform, along with
      the logic to combine them.
      
      The easiest to provide for this is to move the logic and the defaults
      away from Configure and into the build files.
      
      This also means that the definition of the macros ENGINESDIR and
      OPENSSLDIR move away from include/openssl/opensslconf.h and into the
      build files.
      
      Makefile.in is adapted accordingly.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      5482dac9
    • R
      Configure et al: treat C defines separately · bcb1977b
      Richard Levitte 提交于
      With some compilers, C macros are defined differently on the command
      line than on Unix.  It could be that the flad to define them isn't -D,
      it could also be that they need to be grouped together and not be mixed
      in with the other compiler flags (that's how it's done on VMS, for
      example).
      
      On Unix family platform configurations, we can continue to have macro
      definitions mixed in with the rest of the flags, so the changes in
      Configurations/*.conf are kept to an absolute minimum.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      bcb1977b
    • R
      Remove store. · 7984f082
      Rich Salz 提交于
      Rebased and merged by me, with Ben's approval.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      Reviewed-by: NBen Laurie <ben@openssl.org>
      7984f082
    • R
      Make the processing of build.info files more aware of absolute dirs · 2e963849
      Richard Levitte 提交于
      There were cases where some input was absolute, and concatenating it
      to the diretory to the source or build top could fail spectacularly.
      Let's check the input first to see if it's absolute.
      
      And while we're on the subject of checking if a file or dir spec is
      absolute using file_name_is_absolute() has its own quirks on VMS,
      where a logical name is considered absolute under most circumstances.
      This is perfectly correct from a VMS point of view, but when parsing
      the build.info files, we want single word file or directory names to
      only be checked syntactically.  A function isabsolute() that does the
      right thing is the solution.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      2e963849