aboutsummaryrefslogtreecommitdiff
path: root/ports/sqlitecpp/0001-Find-external-sqlite3.patch
diff options
context:
space:
mode:
authorNicole Mazzuca <mazzucan@outlook.com>2019-08-08 16:14:59 -0700
committernicole mazzuca <mazzucan@outlook.com>2019-08-26 12:35:22 -0700
commit782723959399a1a0725ac4921b1b7a7c9d10baf7 (patch)
tree4e611c1b585180f438c692b3bfa367e89bf4a9b6 /ports/sqlitecpp/0001-Find-external-sqlite3.patch
parente417ff69b746f7842b3b9d0fceacb080498e1c5d (diff)
downloadvcpkg-782723959399a1a0725ac4921b1b7a7c9d10baf7.tar.gz
vcpkg-782723959399a1a0725ac4921b1b7a7c9d10baf7.zip
(#7757) [vcpkg] Switch to internal hash algorithms 📜
On non-Windows platforms, there is no standard way to get the hash of an item -- before this PR, what we did was check for the existence of a few common utility names (shasum, sha1, sha256, sha512), and then call that utility on a file we created containing the contents we wish to hash. This PR adds internal hashers for sha1, sha256, and sha512, and standardizes the interface to allow anyone to implement hashers in the future. These hashers are not extremely optimized, so it's likely that in the future we could get more optimized, but for now we just call out to BCryptHasher on Windows, since it's standard and easy to use (and about 2x faster for sha1 and sha256, and 1.5x faster for sha512). However, they are reasonably fast for being unoptimized. I attempted a few minor optimizations, which actually made the code slower! So as of right now, it's implemented as just a basic conversion of the code on Wikipedia to C++. I have tested these on the standard NIST test vectors (and those test vectors are located in vcpkg-test/hash.cpp).
Diffstat (limited to 'ports/sqlitecpp/0001-Find-external-sqlite3.patch')
0 files changed, 0 insertions, 0 deletions