rename binary as blast+ for package coherency.
Last-Updated: 2011-10-03
Gbp-Pq: Name legacy_rename_rpsblast
[PATCH] Allow substituting PCRE2 for legacy PCRE by explicit request.
- For now, require opt-in via --with-components="...;PCRE2;..." (CMake),
--with-pcre2 (traditional Unix build system), or uncommenting the
relevant ThirdParty_PCRE2 setting in project_tree_builder.ini
(traditional Windows build system).
- Likewise, hold off on switching the bundled copy to PCRE2 or checking
for any functions or headers that will become of interest.
- Redundantly (for now) shun external PCRE2 in bin-release configurations.
- Otherwise favor (allowed!) external installations over the bundled
copy, preferring PCRE2 over legacy PCRE when both are found and
allowed but (in due course) external legacy PCRE over bundled PCRE2 in
the absence of external PCRE2.
- In the traditional build system, have the widely used PCRE_LIBS macro
correspond to whichever PCRE is default (when not falling back on a
bundled copy), and add a PCRE_LEGACY_LIBS macro for the sake of
anything using legacy PCRE directly (very occasionally seen).
JIRA: CXX-12761,
git-svn-id: https://anonsvn.ncbi.nlm.nih.gov/repos/v1/trunk/c++@102806
78c7ea69-d796-4a43-9a09-
de51944f1b03
Irrelevant (and inapplicable) changes to c++/src/build-system/cmake/,
c++/src/build-system/configure (which will be regenerated anyway), and
c++/src/build-system/project_tree_builder.ini elided.
Gbp-Pq: Name allow_pcre2
[PATCH] Accommodate Mbed TLS 3.x (specifically, 3.6.0 LTS).
- Conditionally pass mbedtls_pk_parse_key the existing pRNG and its state.
- Call psa_crypto_init during setup, as PSA may be in play even when not
explicitly enabled. Documentation suggests calling it as early as
possible; in practice, though, holding off until after pRNG
initialization avoids "insufficient entropy" errors under 2.x (at least
2.28.8 LTS on Linux) and still works fine as of 3.6.0.
- At least for now, ensure that MBEDTLS_SSL_VERIFY_NONE remains effective
by additionally capping the TLS version at 1.2; as of 1.3, certificate
checking has become mandatory, and Mbed TLS respects that requirement.
- Additional tuneups to ncbi_mbedtls.c-only code:
-- Account for error-code macro repertoire changes by conditionalizing
major-version-specific macros on their availability and specifically
checking for or emitting MBEDTLS_ERR_PLATFORM_FEATURE_UNSUPPORTED (new)
as appropriate,
-- x_ErrorToStatus: Conditionally use MBEDTLS_PRIVATE for p_bio, which has
no accessor.
-- x_MbedTlsWrite: Substitute mbedtls_ssl_get_max_out_record_payload for
mbedtls_ssl_get_output_max_frag_len, which didn't account for other
relevant considerations and is now fully private.
https://github.com/Mbed-TLS/mbedtls/blob/development/docs/3.0-migration-guide.md
supplied useful guidance. JIRA: CXX-13565.
git-svn-id: https://anonsvn.ncbi.nlm.nih.gov/repos/v1/trunk/c++@102329
78c7ea69-d796-4a43-9a09-
de51944f1b03
Gbp-Pq: Name support_mbedtls3
projects / ncbi-blast+.git / log