| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
accepts options 'boost' and 'system'. Now GF(p) math (and indirectly,
ECDSA) will be enabled if --with-tr1=boost or --with-tr1=system
is passed at build time to enable a shared_ptr implementation.
Modules can now specify that they require TR1, in which case
they will only be autoloaded if a TR1 implementation was set
(they can choose which one to use by checking the feature macros
from build.h)
The gfpmath module was set to load only on request. That has
changed to load automatically (but will only do so if a TR1
impl is set as described above). CVC has also been marked
as requiring TR1. (ECDSA/ECDH are not, since they do not
use tr1 shared_ptr directly)
Update and cleanup help output. Do not print the list of modules in
--help anymore (too long); you can still get the list (in an easier to
parse format) --module-info. Reorganize the help text so the more
useful options are described closer to the top.
Fix the --with-endian and --with-unaligned-mem options: they were being
accepted but ignored.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
'/bin/uname', '/usr/bin/uname', or '/bin/sh' - the existence of
these files gives us some hope that exec'ing uname will work,
and avoids an error on Windows builds.
Only run uname once (uname -a), collecting it into $$config{'uname'}
(previously configure.pl might run it as many as three times,
uname -s, uname -p, and uname -m).
Only submodels were being searched longest to shortest. Modify
guess_cpu_from_this to also search arch names and aliases in this
manner. This allows Config{'archname'} of 'x86_64-linux' to be
correctly detected as x86-64 (was being detected as x86, since
before the search was ordered by the Perl hash order).
|
| |
|
| |
|
| |
|
|
|
|
|
| |
longest match first instead of random Perl hash order. Seems to work
very well in practice.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Markus Wanner noted on the mailing list that build.h was not being
installed. That is because it was not included in the HEADERS variable
in the Makefile, and build.h did not yet exist when configure.pl scanned
the source and include directories.
Rearrange the order of operations in configure.pl a bit so first build.h
is generated and then the makefile is.
|
| |
|
| |
|
| |
|
|
|
|
| |
--enable-modules for it to be recognized
|
| |
|
| |
|
| |
|
|
|
|
|
| |
(--bindir, --libdir, --docdir already supported, add --includdir=,
--localstatedir=, etc)
|
| |
|
|
|
|
|
|
|
| |
Suggestions from Zack Weinberg on the monotone-devel list.
Rename --endian to --with-endian
Rename --unaligned-mem to --with-unaligned-mem
|
| |
|
|
|
|
| |
names for CPUs we pulled from the text files.
|
|
|
|
| |
problems on MSYS. And doesn't have any real advantage that I can see...
|
| |
|
|\
| |
| |
| |
| |
| | |
fd327b29aa542e0ad5ff6d37d8392321670f0369)
to branch 'net.randombit.botan.modularized' (head 3f8d05493d4b192243fdc8a7f518ed1013c3be54)
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
that file from another module (without loading it). This was needed since
mp_asm64 and mp_ia32_msvc do not implement both mp_asm.h and mp_asmi.h
like the other mp_ modules - instead they pull the mp_generic version in.
|
| | |
|
| |
| |
| |
| |
| |
| | |
seem to be handled correctly (er, at least mostly), and more importantly
the asm MPI modules are detected and used correctly (at least on x86-64
and x86).
|
| |
| |
| |
| |
| |
| | |
this in and sync'ing before I take a break. However the info.txts are now
cleaned up and more or less accurate now. But configure.pl is not tracking
dependencies properly.
|
| | |
|
| |
| |
| |
| |
| |
| | |
in utils.
Support OS feature macros, eg BOTAN_TARGET_OS_HAS_POSIX_MLOCK (how very autoconf)
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Moved XS, Boost Python, and SWIG wrappers to new toplevel directory 'wrappers'
Moved NIST X.509 test suite into checks directory
Move the build information used by configure.pl to src/build-data
Move scripts directory to doc (for lack of a better spot)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
rather than silently replacing the C++ versions. Instead they are silently
replaced (currently, at least) at the lookup level: we switch off the set
of feature macros set to choose the best implementation in the current
build configuration. So you can have (and benchmark) MD5 and MD5_IA32
directly against each other in the same program with no hassles, but if
you ask for "MD5", you'll get maybe an MD5 or maybe MD5_IA32.
Also make the canonical asm names (which aren't guarded by C++ namespaces)
of the form botan_<algo>_<arch>_<func> as in botan_sha160_ia32_compress,
to avoid namespace collisions.
This change has another bonus that it should in many cases be possible to
derive the asm specializations directly from the original implementation,
saving some code (and of course logically SHA_160_IA32 is a SHA_160, just
one with a faster implementation of the compression function, so this seems
reasonable anyway).
|
|\|
| |
| |
| |
| |
| | |
ca7d7fc1ae6b55c5328c9cf1ec1cafd1daadedd4)
to branch 'net.randombit.botan.modularized' (head 614263a9742a0c554e4093620147f6e156264d41)
|
| | |
|
| |
| |
| |
| | |
Derek Scherger
|
| |
| |
| |
| |
| | |
them modules now. In any case there is no distinction so info.txt seems
better.
|
| |
| |
| |
| |
| | |
a lot of public key stuff in here that needs to be extracted however,
and probably 2-3 other modules worth of stuff to split off (engines, etc)
|
| | |
|