aboutsummaryrefslogtreecommitdiff
path: root/src/Makefile.test.include
AgeCommit message (Collapse)Author
2015-01-08tests: run sanity checks in tests tooCory Fields
If these are going to fail in bitcoind, they should fail in the tests as well. Github-Pull: #5604 Rebased-From: d58c5d6f21fd2421bc8cbb224849e8c38b617775
2015-01-06bitcoin-tx: Fix JSON validation of prevtxsEric R. Schulz
Github-Pull: #5528 Rebased-From: 2a3d988b802dcea4453241e37168d8511078940a a089c50981e822014ffc18e8a37b3518feb52206 2c14d1532fe66a243cdbfb7de48b298213305765
2014-11-20build: fix link error on some platforms. Fixes #5235Cory Fields
Some users may have libtool libs (.la) installed in their linker search paths. In this case, using -static-libtool-libs would try to link in .a's instead of shared libs. That would be harmless unless the .a was built in a way that would break linking, like non-fpic. What we really want is "-static" here. Despite its name, it's actually less aggressive than -static-libtool-libs. It causes only internal libs to be linked statically (libbitcoinconsensus is the one were'a after).
2014-11-19build: add --with-libs so that libs are optionalCory Fields
2014-11-19build: add libbitcoinconsensus files and hook up the lib buildCory Fields
Credit BlueMatt for libbitcoinsonsensus.h/cpp
2014-11-19build: make a distinction between static app ldflags and static lib ldflagsCory Fields
For windows builds, exe's are always static, but libs should still conform to --enabled-shared and --enable-static.
2014-11-18build: secp256k1 as a subdir, since it's requiredCory Fields
2014-11-18Always build and link libsecp256k1Pieter Wuille
2014-10-31minor cleanup: include orders, end comments etc.Philip Kaufmann
- no code changes
2014-10-13build: quit abusing LIBS for Windows builds.Cory Fields
Similar to the INCLUDES changes in 6b099402b40, split out LIBS into individual entries for more fine-grained control. Also add MINIUPNPC_LIBS which was missing before, and hook it up to executables.
2014-10-08Make SCRIPT_VERIFY_STRICTENC compatible with BIP62Pieter Wuille
* Delete canonical_tests.cpp, and move the tests to script_tests.cpp. * Split off SCRIPT_VERIFY_DERSIG from SCRIPT_VERIFY_STRICTENC (the BIP62 part of it). * Change signature STRICTENC/DERSIG semantics to fail the script entirely rather than the CHECKSIG result (softfork safety, and BIP62 requirement). * Add many autogenerated tests for several odd cases. * Mention specific BIP62 rules in the script verification flags.
2014-09-23Add coins_tests with a large randomized CCoinViewCache test.Pieter Wuille
2014-09-14bitcoin-util-test: Test bitcoin-tx with null scriptPubKeyLuke Dashjr
2014-08-26Move CMedianFilter to timedata.cppWladimir J. van der Laan
Now that we no longer use the median filter to keep track of the number of blocks of peers, that's the only place it is used.
2014-08-22Merge pull request #4733Jeff Garzik
2014-08-20UniValue: add unit testsJeff Garzik
2014-08-19Add bitcoin-tx testsJeff Garzik
Testing: delin, delout, locktime, and basic createrawtransaction-like functionality.
2014-08-19Add "it works" test for bitcoin-txJeff Garzik
2014-08-18build: add option for reducing exports (v2)Cory Fields
This was committed previously as 4975ae172 and reverted, because the flags were applied even if the checks didn't pass. This is the same commit, fixed up to actually disable the functionality when necessary. Enabled automatically if boost >= 1.49. See: https://svn.boost.org/trac/boost/ticket/2309 Also, check for a default visibility attribute, so that we can mark future api functions correctly.
2014-08-18Revert "build: add option for reducing exports"Wladimir J. van der Laan
Revert #4663 for now. It still breaks the pulltester. This reverts commit 4975ae1722cd8af63eda2f02ef64a98091b6fb58. Conflicts: configure.ac
2014-08-15build: add option for reducing exportsCory Fields
Enabled automatically if boost >= 1.49. See: https://svn.boost.org/trac/boost/ticket/2309 Also, check for a default visibility attribute, so that we can mark future api functions correctly.
2014-08-15build: fix automake warnings about the use of INCLUDESCory Fields
While we're at it, reduce the use of LIBS as well. This makes dependencies explicit. Fixes building with (the not-yet-merged) libsecp256k1 as well. Github-Pull: #4689 Rebased-By: Wladimir J. van der laan <laanwj@gmail.com> Rebased-From: 909b347 c0e5dda
2014-07-29Add "bitcoin-tx" command line utility and supporting modules.Jeff Garzik
This is a simple utility that provides command line manipulation of a hex-encoded TX. The utility takes a hex string on the command line as input, performs zero or more mutations, and outputs a hex string to standard output. This utility is also an intentional exercise of the "bitcoin library" concept. It is designed to require minimal libraries, and works entirely without need for any RPC or P2P communication. See "bitcoin-tx --help" for command and options summary.
2014-07-01secp256k1: Add build-side changes for libsecp256k1Cory Fields
Note: This is added to our existing automake targets rather than as a libtool-style lib. The switch to libtool-style targets can come later if it proves to not add any complications.
2014-06-29Add skiplist unit testsPieter Wuille
2014-06-25Remove unnecessary dependencies for bitcoin-cliWladimir J. van der Laan
This commit removes all the unnecessary dependencies (key, core, netbase, sync, ...) from bitcoin-cli. To do this it shards the chain parameters into BaseParams, which contains just the RPC port and data directory (as used by utils and bitcoin-cli) and Params, with the rest.
2014-06-21crypto: create a separate lib for crypto functionsCory Fields
This lib has no dependencies on other bitcoin functionality. Attempting to use bitcoin headers will result in a failure to compile.
2014-06-21Extend and move all crypto tests to crypto_tests.cppPieter Wuille
2014-06-21Add built-in SHA-1 implementation.Pieter Wuille
2014-06-21Add a built-in SHA256/SHA512 implementation.Pieter Wuille
This also moves the HMAC-SHA512 implementation to sha2.cpp.
2014-06-05build: quit abusing AM_CPPFLAGSCory Fields
Now that the build is non-recursive, adding to AM_CPPFLAGS means adding to _all_ cppflags. Logical groups of includes have been added instead, and are used individually by various targets.
2014-06-05build: avoid the use of top_ and abs_ dir pathsCory Fields
Using them has the side effect of confusing the dependency-tracking logic.
2014-06-05build: nuke Makefile.include from orbitCory Fields
Rules and targets no longer need to be shared between subdirectories, so this is no longer needed.
2014-06-05build: Switch to non-recursive makeCory Fields
Build logic moves from individual Makefile.am's to include files, which the main src/Makefile.am includes. This avoids having to manage a gigantic single Makefile. TODO: Move the rules from the old Makefile.include to where they actually belong and nuke the old file.