You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the library in a somewhat unconventional way. Note that I have not tried compiling with the stock Makefile utils that come bundled with the library. Basically I only need a few of the crypto methods, so I am extracting these couple of directories into my source, and compiling them with my project's own standalone Makefile.
This seems to work well, with the exception of a caveat I just ran into trying to compile this way: In the des/des.*{c,h} files, there is a discrepancy in a few of the functions with the way the key buffers are typed: sometimes it's void *key, others it's uint8_t *key. This caused avr-gcc to issue me an error, so I thought to pass it on to the developers.
Overall, the library seems to be very neatly coded and minimal enough that other crypto overhead can be built on top of it. Thanks.
The text was updated successfully, but these errors were encountered:
Hello.
I am using the library in a somewhat unconventional way. Note that I have not tried compiling with the stock Makefile utils that come bundled with the library. Basically I only need a few of the crypto methods, so I am extracting these couple of directories into my source, and compiling them with my project's own standalone Makefile.
This seems to work well, with the exception of a caveat I just ran into trying to compile this way: In the
des/des.*{c,h}
files, there is a discrepancy in a few of the functions with the way the key buffers are typed: sometimes it'svoid *key
, others it'suint8_t *key
. This causedavr-gcc
to issue me an error, so I thought to pass it on to the developers.Overall, the library seems to be very neatly coded and minimal enough that other crypto overhead can be built on top of it. Thanks.
The text was updated successfully, but these errors were encountered: