Okay.  Please look at extending cmCryptoHash to offer access to
the _Final functions to get the binary digests directly as
`std::vector<unsigned char>` or something like that.  That will
avoid the binary->hex->binary conversion sequence before going
to Base64.  Also, please explain the motivation in comments.

These patches change the private abstract interface of cmCryptoHash to return std::vector<unsigned char> instead of std::string.
Conversion to std::string is handled by a static public method.

-Sebastian


Attachment: cmake_3-6-1_cmCryptoHash_patches_v001.tar.gz
Description: application/gzip

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Reply via email to