| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
This makes setting LD_LIBRARY_PATH obsolete when Botan lib and botan
/botan-test binary are in the same directory. This behavior is default
on Windows.
LD_LIBRARY_PATH can still be used to override the RPATH.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Remove unused make variables VERSION, BRANCH
- Move first make all target below all variable definitions
- Move "Executable targets" as well as "LIBNAME" from header.in into
gmake.in and nmake.in. Those variables differ more than they share
and are getting too abstract.
- Use new variable names: LIB_BASENAME, LIB_FILENAME. Drop LIBNAME and
BOTAN_LIB
- Write libs to out_dir now, which enables out-of-tree builds
GH #110, replaces #70 #106 #107 fixes #85
|
| |
|
|
|
|
| |
value set in header template. GH #107
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
alternate implementation for Unix and add some feature checks so a
boost-free build of the tests and command line are possible again.
|
|
|
|
|
|
|
|
|
|
|
|
| |
ctypes Python wrapper that uses it. The API is intentionally designed
to have a very simple ABI (extern "C", all structs are opaque, no
memory ownership passing the FFI boundary, limited set of simple types
as args) so the ctypes wrapper is quite simple.
Currently ffi provides ciphers, hashes, MACs, RNGs, PBKDF, KDF,
bcrypt, and most public key operations.
Remove the old boost.python wrapper and all the build code for it.
|
|
|
|
| |
with some modifications by randombit.
|
| |
|
| |
|
|
|
|
|
|
| |
rather than the base destdir. Pointed out by hexchain in github pull 38.
Version the docdir with the full version incl patch.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Add `website` target to makefile.
Some progress towards fixing minimized builds.
TLS now hard requires ECDSA and GCM since otherwise a minimized build
has only insecure options.
Remove boost_thread dependency in command line tool
|
| |
|
|
|
|
| |
the tests and botan for everything else.
|
|
|
|
|
| |
Renamed make target to gmake because I'm pretty sure += and
ifdef on variables is gmake specific.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
test. Update to new AEAD api. Currently requires boost_regex (for
tests only), done via hardcoding in makefile template.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
compiler and target platform might support it. For instance the AES
SSSE3 code is now always in any x86 build, with just that specific
file being compiled with -mssse3. Since we'll only call that code if
cpuid confirms it works at runtime, we don't have portability issues,
and it can be safely included in generic builds (eg for distributions).
Tweak how machine specific compiler flags are generated to be a bit
easier to maintain.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
maintainer.
Namespace the headers in /usr/local/include/botan-1.9/botan, so
multiple versions can be installed in parallel.
Down version to 1.9.18 since there are a good number of changes in
this release already.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
proper. Enabled using --use-sphinx and --use-doxygen options, both of
which default to false. If Sphinx isn't enabled, the ReST sources are
copied directly (a case where having a very readable source format
comes in handy...)
The reference manual (either Sphinx processed into HTML, or the raw
source) and the Doxygen output (if enabled) are copied into the doc
directory upon install on Unix. Currently not done on Windows, the
install target is fairly bogus there currently, and hasn't been tested
in some time.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
More documentation updates.
The clean target wasn't removing one of the symlinks.
In the self-test application, warn if the version we are linked
against does not match the version we were built against. This
always indicates a problem. Someone who had an older version
installed on their system got very confused when the test app was
linked against it at runtime; this warning would have saved a
couple hours of puzzling by me. This would also have helped avoid
the nasty bug in 1.8.3
|
| |
|
|
|
|
| |
match the norman Unix conventions.
|
| |
|
| |
|