aboutsummaryrefslogtreecommitdiffstats
path: root/configure.py
Commit message (Collapse)AuthorAgeFilesLines
* Dirty hack to support multiple 'define' options in a module info file.lloyd2011-12-231-8/+16
| | | | | | | | If the default value is a list we will append to it instead of overwriting it. (Previouly, multiple define targets 'worked' with last one winning as the values were progressively overwritten). This might be useful for other things, compiler warning options maybe?
* Warn the user if targetting for GCC on Windows without an explicitlloyd2011-12-021-9/+12
| | | | | --os=windows since likely they actually wanted either --os=cygwin or --os=mingw
* Log the detected revision, if mtn reports somethinglloyd2011-11-101-0/+2
|
* PyPy workslloyd2011-11-091-7/+6
|
* Switch to the Python 3 syntax in configure.py. A Perl one-liner in thelloyd2011-10-181-10/+12
| | | | header shows how to return it to 2.5 compatability.
* If running a non-released version and monotone wasn't installed (orlloyd2011-10-181-9/+16
| | | | | wasn't in path), get_vc_revision would not catch an OSError exception from subprocess and the whole configure would fail
* Python 3.1's subprocess.Popen.communicate returns a bytes rather thanlloyd2011-10-101-2/+5
| | | | a str. Sigh.
* Search for an exact match in both arch and submodel before tryinglloyd2011-08-191-4/+15
| | | | | regex matching. Increases the odds we'll get the correct/intended target. Debian bug 638347.
* Initialize the logger before we call parse, so if an exception getslloyd2011-07-211-3/+4
| | | | | thrown out of there it will be formatted properly. Then set the level after getting the arguments.
* Allow overriding the VC revision in botan_version.py (for releases)lloyd2011-07-111-1/+1
|
* Tick to 1.10.1 unreleased.lloyd2011-06-301-5/+20
| | | | | Try to detect the mtn revision (by shelling out to mtn automate), and including it in build.h as BOTAN_VERSION_VC_REVISION.
* Fix building with --via-amalgamation; it wouldn't generate thelloyd2011-06-031-14/+12
| | | | | | | | amalgamation properly, but would happen to work if a previously written amalgamation was around. Also make changes allowing using the SIMD optimized versions of SHA-1 and Serpent to be used in the amalgamation.
* Add --via-amalgamation option that builds everything from a singlelloyd2011-06-011-16/+31
| | | | source file.
* Use visibility control unless explicitly turned offlloyd2011-05-311-0/+3
|
* Split the SIMD implementations into their own modules and choose onelloyd2011-05-241-9/+8
| | | | at config time.
* Add (undocumented) option --no-optimizations which turns off alllloyd2011-05-131-9/+18
| | | | compiler optimizations in the build.
* Modify soname to match Unix conventions at suggestion of Debianlloyd2011-05-121-2/+10
| | | | | | | | | | 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.
* Disable CMS by default, since it's pretty untested and likely unusablelloyd2011-05-061-4/+12
| | | | | | | | currently. Include the source directory name in object file names. Add some more DES test vectors.
* Print comments only on modules that will be usedlloyd2011-05-031-2/+7
|
* When building for GCC, always get the version number, and turn off TR1lloyd2011-05-031-20/+60
| | | | | | | | | | | and -fvisibility support if the version is too old. You can also turn them off explicitly with the (hidden) option --without-visibility. We get the version number from the binary specified with --cc-bin, if the user set that, rather than from plain 'g++'. Fix Solaris install - apparently 'install' cmd is broken/dumb. Fix Ekopath flags for submodels.
* Log the chosen MP modulelloyd2011-04-291-0/+3
|
* Add new options --cc-bin for setting the name/path to the compilerlloyd2011-04-291-6/+14
| | | | binary. Nicer than having to edit the makefile...
* Log that we are assuming the existence of TR1 during configurelloyd2011-04-291-6/+11
|
* Document KDF properly.lloyd2011-04-221-1/+2
| | | | | | | | Split log by release series instead of year. Make dedicated landing page. If SPHINX_OPTS is set, it will be passed to sphinx-build
* Some small cleanups in output. Fully namespace optparselloyd2011-04-221-32/+32
|
* Intel C++ doesn't seem to have an option for setting the soname, so itlloyd2011-04-221-1/+1
| | | | | | | | | | | | will default to the full output file name. That actually worked as expected when the so was always written as libbotan-1.8.2, but doesn't anymore since soname does not match the written file. This probably won't work right on Windows, but I don't have access to Intel C++ on Windows. Note good Intel C++ 11.1 build in build log Note that CPython 2.7 works for configuring the build
* Enable unix_procs for FreeBSD. It was disabled in 2006 to worklloyd2011-04-211-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | around a bug in FreeBSD 6.1, which is long EOL. If we can't figure out the CPU in configure.py, if running verbosely dump the entire list of CPUs we know about. Some doc cleanups. Rename the 'beos' target to 'haiku', since testing shows that botan can't compile under the old BeOS GCC 2.95 anyway. Remove the call to idle_time in the stats entropy source - it causes a crash on Haiku R1-alpha2 somewhere inside a system DLL. I didn't bother debugging it beyond looking at the backtrace. Add a 'bepc' alias for i386 as that is what Haiku reports its processor as. Fix the install dirs to match Haiku R1, though apparently they will change in R2 anyway when they add package management. Enable use of gmtime_r on Haiku.
* Fix the --without-sphinx and --without-doxygen flags.lloyd2011-04-191-21/+30
| | | | | | | If neither --with-sphinx nor --without-sphinx were used, then test for sphinx-build in the path and turn it on if we find it. Document the --distribution-info option.
* Rename --use-sphinx and --use-doxygen to --with-sphinx andlloyd2011-04-181-8/+14
| | | | | --with-doxygen, and add no-op --without versions for both. This makes it easier to script the build in Gentoo's ebuild.
* Integrate building docs using Sphinx and Doxygen into the makefilelloyd2011-04-181-21/+44
| | | | | | | | | | | | | 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.
* Docs list is hardcoded into configure.py, and was out of date WRTlloyd2011-04-151-10/+3
| | | | recent changes. Just copy all .txt files from doc and call it good...
* I think this fixes the soname stufflloyd2011-04-111-12/+5
|
* I belive this check in fixes PR 113 by making shared library sonameslloyd2011-04-061-2/+2
| | | | match the norman Unix conventions.
* Convert most of the documentation to reStructured Text, addinglloyd2011-04-041-6/+12
| | | | | | | | | | | | | | | | | | | a makefile to build it with Sphinx (http://sphinx.pocoo.org/). Previously credits.txt listed public domain code sources; instead directly credit the authors in the relevant files and delete that file. Drop the draft FIPS 140 security policy; I can't imagine FIPS 140 validation will ever happen, and if it does, I don't want anything to do with it. Also drop the internals doc, which was so out of date (and incomplete) as to be worthless. Move the tutorials and InSiTo pdfs into old/ for the time being, until anything relevant from them can be filtered out and converted into RST.
* Tick to 1.9.16-devlloyd2011-03-211-4/+4
|
* Update notes, version, and readme for 1.9.15, first release candidate1.9.151.10.0-rc1lloyd2011-03-211-2/+2
| | | | for 1.10.0
* Print a warning when SSL is enabled, as it is new and mostlylloyd2011-03-211-2/+8
| | | | | unreviewed/untested at this point. Add support for a <comment> tag for this.
* Shared lib should be marked as a dev releaselloyd2011-03-141-1/+1
|
* Tick to 1.9.15-devlloyd2011-03-071-3/+3
|
* Update amalgamation copyright yearslloyd2011-03-021-1/+1
|
* Tick version numbers for 1.9.14 release1.9.14lloyd2011-03-011-2/+2
|
* Add a new option --link-method which allows the user to override thelloyd2011-02-181-5/+34
| | | | | method by which include files are linked into the build directory. Handy for working around bugs and corner cases.
* Typo fixlloyd2011-02-181-2/+2
|
* Canonicalize OS name for Cygwin; apparently platform will reportlloyd2011-02-181-0/+5
| | | | things like cygwin_nt-5.1 in some cases.
* Warn about unknown modules passed to --enable-modules or --disable-moduleslloyd2011-02-111-0/+8
|
* Tick version to 1.9.14-devlloyd2011-02-101-4/+4
|
* Tick to 1.9.13 release1.9.13lloyd2011-02-091-2/+2
|
* Add a new configure.py option --distribution-info which sets a macrolloyd2011-02-071-6/+8
| | | | | | | | | | | | | | | | | | | | | | | in build.h named BOTAN_DISTRIBUTION_INFO. The default value is 'unspecified'. People packaging botan could set this to another value, for instance 'Gentoo 1.9.13-r3' or 'Debian 1.9.13-1', or 'pristine' to indicate a completely unmodified/stock version. This was suggested by Zooko for Crypto++ in http://sourceforge.net/apps/trac/cryptopp/ticket/11 and seemed like an idea worth stealing. Don't default the version datestmap to the current day if unset, instead set to zero. This allows applications to detect unreleased versions. Document that version_datestamp will return zero for unreleased versions. Change the version_string function to return more information about the current version, including the release date and distribution information. It will now return strings like: Botan 1.9.13 (released 20110207, distribution Gentoo 1.9.13-r3) or for an unreleased version: Botan 1.9.13 (unreleased version, distribution unspecified)
* Apply a patch to configure contributed by Lyon Chen in PR 134.lloyd2011-02-071-1/+1
| | | | | This doen't fix all the cases were bogus symlinks are generated, but it helps one particular useful case.
* If there is a malformed or missing header guard, raise an error withlloyd2010-12-281-2/+5
| | | | an informative message rather than dying with an index error.