aboutsummaryrefslogtreecommitdiffstats
path: root/configure.pl
Commit message (Collapse)AuthorAgeFilesLines
* Change version to 1.8.6-pre, document changes since 1.8.5 releaselloyd2009-07-251-3/+3
|
* Update log, readme, version #s in configure for 1.8.5 release 2009-07-231.8.5lloyd2009-07-231-2/+2
|
* In both configures, strip out periods in submodel names for generating thelloyd2009-07-231-0/+1
| | | | | | | | | TARGET_CPU_IS macro. This would otherwise cause problems on HP-PA, as it would generate invalid macros like TARGET_CPU_IS_HPPA2.0 Also in configure.py, replace hyphens with underscores in the submodel name for generating the macro (configure.pl already did this). Otherwise using the sparc64-ultraX submodels would also generate an invalid macro in build.h
* Fix ticket 46lloyd2009-07-211-8/+13
| | | | | | | | | | | Previous behavior was that if a module was explicitly disabled, the libraries that module used would still be linked in. So for instance configure.pl --disable-modules=pthreads --without-openssl would cause libpthread and libcrypto to be included in the final link! This bug only affected the Perl configure
* Set version fields for 1.8.5 rc1lloyd2009-07-211-2/+4
|
* Fix dependency resolution in configure.pl (same algorithm as configure.py)lloyd2009-07-171-61/+32
| | | | | | | | Fix --enable-asm (had same effect as --disable-asm) Fix mp_bits calculation; took into account both modules which were enabled and ones that were explicitly disabled, for instance ./configure.pl --disable-modules=mp_amd64 -> mp_bits == 64
* New module load_on directive 'never', to mark known-buggy codelloyd2009-07-151-0/+1
|
* Bump version numbers to 1.8.5-prelloyd2009-07-141-2/+2
|
* Update configure.pl's version #1.8.4lloyd2009-07-121-1/+1
|
* Also match GCC 4.4 for -fpermissive checkslloyd2009-07-081-1/+1
|
* Correct detection of GCC 2.95 for setting -fpermissive. This had beenlloyd2009-07-081-1/+1
| | | | | wrong for a while, which suggests perhaps that 2.95 has finally died out in the wild. Praise be.
* configure.py seems close enough to functional to me that I'm going tolloyd2009-07-021-0/+4
| | | | | | officially deprecate the Perl configure, though it probably won't be removed until a development tree release since otherwise will break distro packaging scripts.
* Minor hackery to deal with win32 library dependencieslloyd2009-07-021-3/+2
|
* Minimal changes to configure.pl to deal with altered templates in build.hlloyd2009-07-021-3/+24
| | | | for macro generation.
* Change the makefile template language somewhat. Previously variableslloyd2009-07-011-34/+25
| | | | | | | | | | | | | | | | | 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).
* Make the install_cmd_{data,exec} items in the build-data files quoted,lloyd2009-07-011-4/+4
| | | | | | | | | | | 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.
* Allow for the shared library soname to stay fixed even when the versionlloyd2009-05-131-1/+6
| | | | number increments, for stable releases that don't affect binary compat.
* Bump version to 0.8.3-prelloyd2009-04-161-1/+1
|
* Bump to 1.8.2-prelloyd2009-01-211-1/+1
|
* Bump version in configure and readme to 1.8.1-prelloyd2009-01-031-1/+1
|
* Rickard Bondesson reported on botan-devel about some problems buildinglloyd2008-12-021-2/+2
| | | | | | | | | | | | | | | | | | | | on Solaris 10 with GCC 3.4.3. First, remove the definition of _XOPEN_SOURCE_EXTENDED=1 in mmap_mem.cpp and unix_cmd.cpp, because apparently on Solaris defining this macro breaks C++ compilation entirely with GCC: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6395191 In es_egd.cpp and es_dev.cpp, include <fcntl.h> to get the declaration of open(), which is apparently where open(2) lives on Solaris - this matches the include the *BSD man pages for open(2) show, though AFAIK the BSDs all compiled fine without it (probably due to greater efforts to be source-compatible with Linux systems by *BSD developers). I have not been able to test these changes personally on Solaris but Rickard reports that with these changes everything compiles OK. Update lib version to 1.8.0-pre. ZOMG. Finally.
* Consolidate the useful stuff from doc/info.txt into readme.txtlloyd2008-11-301-1/+1
|
* Document changes since 1.7.23. Bump version number to 1.7.24-pre; I'lllloyd2008-11-241-1/+1
| | | | | decide later on if changes warrant another release candiate or not. If not, 1.7.24 will be remarked as 1.8.0 prior to release.
* If configure.pl guesses the CPU using /proc/cpuinfo or uname, it remindslloyd2008-11-241-2/+3
| | | | | | | | the user that it can override via --cpu, however if it was guessed using Config{'archname'} the user was not so reminded. This is actually the worst possible case since Perl's Config setting is probably the least reliable method (which is why it is only used if /proc/cpuinfo and uname are not around).
* Add handy aliases to configure for controlling the modules using OpenSSL,lloyd2008-11-231-0/+9
| | | | | | | | | | | | | | GNU MP, zlib, and bzip2. --with-{openssl,gnump,bzip2,zlib} --without-{openssl,gnump,bzip2,zlib} They have the exact same effect as --enable-modules=x or --disable-modules=x This turned out to be a much easier way of specifying options for the Gentoo ebuild. It is likely that other distro builds architectures will also prefer this option style as being somewhat more autoconf-like and fitting in with existing command templates.
* Make it optional to provide an argument to --enable-modules orlloyd2008-11-211-2/+2
| | | | | | --disable-modules. While updating the Gentoo ebuild I found it was much easier to autogen the configure line if both of these options are no-ops if used with no value.
* Wrap long lines in configure.pl outputlloyd2008-11-191-10/+46
| | | | | | Print the version number at the start of the build. Fix compiler name in TR1 message
* Wrap line for readabilitylloyd2008-11-171-1/+2
|
* Use TR1 by default with GNU C++ and Intel C++, since all recent versions oflloyd2008-11-171-9/+20
| | | | | | | | | | | | | | | | | | 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.
* Bump version to 1.7.23-prelloyd2008-11-171-1/+1
|
* Don't namespace botan-config by major/minor versions (use pkg-config for ↵lloyd2008-11-131-2/+1
| | | | this if desired)
* Remove support for provider identifiers from SCAN_Name - it turns out thislloyd2008-11-121-1/+1
| | | | | | | | | | | | was not the right place to keep track of this information. Also modify all Algorithm_Factory constructor functions to take instead of a SCAN_Name a pair of std::strings - the SCAN name and an optional provider name. If a provider is specified, either that provider will be used or the request will fail. Otherwise, the library will attempt best effort, based on user-set algorithm implementation settings (combine with benchmark.h for choosing the fastest implementation at runtime) or if not set, a static ordering (preset in static_provider_weight in prov_weight.cpp, though it would be nice to make this easier to toggle).
* Tick version to 1.7.21-prelloyd2008-11-091-1/+1
|
* For pkg-config, name as botan-$major.$minor.pc, eg botan-1.7, rather thanlloyd2008-11-071-4/+4
| | | | | botan-17, which was potentially confusing (and apparently contradictory to normal pkg-config naming conventions).
* Fix syntax problems introduced in 80 column wraplloyd2008-11-071-5/+2
|
* Wrap to 80 columnslloyd2008-11-071-17/+31
|
* Print a message that a makefile was created, so it's clear what to dolloyd2008-11-071-1/+1
|
* Put automatically generated botan-config and pkgconfig files into build/lloyd2008-11-071-2/+6
| | | | instead of in the toplevel directory.
* Fix the --with-build-dir option, so that it is actually possible to dolloyd2008-11-061-7/+7
| | | | | | | | | | | | out of tree builds. Also rename the generated botan-config script so that it is, like the pkg-config settings, namespaced by the major and minor version numbers (eg, botan-17-config). This is useful in particular for distros like Debian which ship both stable and unstable versions. Currently Debian is actually the only distro I know of shipping 1.7 as well as 1.6, but I would certainly like to encourage more in the future by making it easy to do.
* Reset version as 1.7.20-prelloyd2008-11-061-1/+1
|
* Provide pkg-config file as botan-$major$minor.pc, so it can be used like:lloyd2008-11-061-15/+19
| | | | | | | $ 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.
* Bump version to 1.7.19-prelloyd2008-10-261-1/+1
|
* If we match /proc/cpuinfo or uname against a submodel alias, instead printlloyd2008-10-231-1/+6
| | | | | the submodel it is referencing - this is usually more recognizable. Suggested by Markus Wanner.
* Allow setting an environmental variable CPUINFO to override the namelloyd2008-10-231-0/+11
| | | | | | of /proc/cpuinfo in configure.pl This is probably only useful for testing.
* Add pkg-config support (requested/suggested by Zack Weinberg on monotone-dev)lloyd2008-10-151-0/+10
|
* Warn if an unknown value is passed to configure.pl's --with-tr1-implementation,lloyd2008-10-141-0/+3
| | | | rather than silently ignoring it.
* Add basic support for Doxygen, including a make targetlloyd2008-10-131-0/+6
|
* Add a new switch to configure.pl --with-tr1-implementation whichlloyd2008-10-121-51/+84
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* Reenable /proc/cpuinfo CPU detectionlloyd2008-10-111-1/+1
|
* Comment out or remove some of the louder/less useful trace messageslloyd2008-10-111-6/+3
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-23 19:39:30 +0000