| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
included on link
|
|
|
|
|
|
| |
put it into build/, and the makefiles still expected it to live in
doc/. Change it so everything uses build/ as the location for the doxy
file. Reported by Markus Reichelt.
|
|
|
|
|
|
| |
change and haven't tested it as I don't have access to any Macs on
hand, but it's being used downstream by MacPorts, and I assume they
know what they are doing.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
scope; this affects Clang and some older GCCs.
Add build support for Clang compiler (untested).
|
|
|
|
|
|
| |
because the Win32 build is still only for static libs in 1.8
Tick version to 1.8.9-dev
|
| |
|
|
|
|
|
|
| |
such in configure.py. Paul Clark reported on the list having problems with
it otherwise because of CVS droppings being picked up and subsequently
errored on when parsing them as build info files (of course) failed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
systems. This was something that for whatever reason that I have
long since forogotten was a good idea on IRIX running MIPS circa
a decade ago, but was reported to cause problems on the Debian
builds.
Add mipsel as an alias for the mips32 architecture for Debian.
The mips32 submodel names were badly typoed and did not work
correctly.
Remove the leading mips32- and mips64- from MIPS submodel names.
|
|
|
|
|
|
|
| |
based on the SGI Pro64 and Pathscale EKOpath compilers. Only tested on an
x86-64 system running Linux (v4.2.1). Miscompiles a few of the block ciphers
(segvs, didn't bother to diagnose further; recompile with -O1 to fix), other
than that seems OK.
|
|
|
|
| |
Contributed by Patrick Georgi
|
|
|
|
|
| |
Python configure scripts. Previously Python version would give up, and
the Perl one would guess i686 (!)
|
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
db0cdfa10718d2065e52b6753d1d671b71cb423d)
to branch 'net.randombit.botan.python-configure' (head f106b1e4c7361a0fee6856defb01a9f96a2fd4eb)
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
had been denoted with @{var:NAME}, this has changed to %{NAME}. This is
pretty much a wash for configure.pl but it makes it much easier to process
the templates using Python's string.Template. The logic being the 'var:'
prefix had been to support conditional statements in the templates (using
an 'if:' prefix), but this functionality was not being used and support
for it is removed from configure.pl in this revision.
For a similiar reason, rename a number of template variables with hyphens
in their name to use underscores instead. This is slightly more consistent
anyway (since many variable names had already used _ instead of -) but more
importantly makes them much easier to deal with using aforementioned Python
template code.
This should not result in any user-visible change (unless I messed up).
|
|
|
|
|
|
|
|
|
|
|
| |
since they often contain spaces. This doesn't matter to configure.pl's
hand-done regex 'parser', but it makes things more consistent and makes
it possible to use the shlex parser included with python to parse all of
the data files.
Also remove the unused <arch> entry in darwin - this information had
previously be removed from all the other files but I guess that one was
missed.
|
|
|
|
|
| |
but with the most recent change to decouple version # and so version this
is wrong - use @{var:so_version} instead.
|
| |
|
|
|
|
| |
number increments, for stable releases that don't affect binary compat.
|
|
|
|
|
|
|
| |
botan-config --libs - with shared objects it makes no difference, but
with static libs this doesn't bring in the needed symbols correctly since
only symbols needed by earlier objects on the command line are brought
in. Reported by Thomas Moschny.
|
|
|
|
| |
somewhat cleaner .so dependencies on ELF systems. Patch from Zack Weinberg.
|
|
|
|
|
|
| |
printfs would complain because it would think that the -L/lib/dir was
an (unknown) option instead of the string. Instead use a plain echo in
each branch of the if, slight code duplication but not a huge deal.
|
|
|
|
|
|
|
| |
because that totally breaks with static libs. OTOH, not using the version
number totally breaks if more than one version is installed.
Kind of a tradeoff...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
both support TR1 fine AFAICT.
Add ability to explicitly disable using TR1 with --with-tr1=none
Add a marker in the cc info files specifiying if TR1 should be chosen
by default. Yes, autoconf would be better for this than a static
per-compiler setting. Yes, I totally hate autoconf. Yes, I would still
consider autoconf patches. No, I'm not going to do it myself. :)
I am looking forward to being able to safely adopt C++0x and TR2
throughout the library and make the need for a lot of this special-casing
stuff go away.
Until then, it seems better to defaulting to using tr1 (and thus, ECC) than
not.
|
| |
|
| |
|
|
|
|
| |
instead of runtime configurable.
|
|
|
|
|
|
|
|
| |
so we link against the specific intended version of the library, for instance
-lbotan-1.7.20 rather than simply -lbotan
This again seems especially an improvement where you want more than one
version installed (1.6 vs 1.7, for instance).
|
| |
|
| |
|
|
|
|
|
|
|
| |
$ pkg-config botan-17 --libs
-L/usr/local/lib -lbotan -lm -lpthread -lrt
to make it easier to have multiple versions of Botan installed and in
use at the same time.
|
|
|
|
| |
detected (as on FreeBSD)
|
| |
|
|
|
|
| |
most Intel Core Duo (32 bit, as opposed to Core 2 Duo being 64 bit).
|
| |
|
| |
|