Steffen Jaeckel
09c4d4c93b
@rofl0r @ [1] "...still it's unusual/unexpected to embed DESTDIR in LIBPATH etc. where this could hickup is when for example hardcoded paths need to be embedded into the resulting binary. for example, in the netbsd-curses makefile i linked earlier, such a case would be reference to the terminfo DB location, which is derived from PREFIX. other possible cases might be stuff that dlopen()s its own libs using an absolute path, or uses other data files. for such a case a contributor would typically re-use DATAPATH oslt and put it into CPPFLAGS or write it into a header, to find the required files. when now these paths have DESTDIR in them too, this will not work. thus it is good practice to use $(DESTDIR) only in install targets, and keep it out of other vars." [1] https://github.com/libtom/libtomcrypt/commit/8e29a6061f3ad7bc7c5c2aeae73705e890ce1ea9#commitcomment-22678488 This closes #232
libtomcrypt
See doc/crypt.pdf for a detailed documentation
Project Status
develop: 
Submitting patches
Please branch off from develop if you want to submit a patch.
Patch integration will be faster if tests and documentation are included.
Please update the makefiles in a separate commit. To update them simply run the updatemakes.sh script.
Branches
Please be aware, that all branches besides master and develop can and will be force-pushed, rebased and/or removed!
If you want to rely on such an unstable branch, create your own fork of this repository to make sure nothing breaks for you.