aboutsummaryrefslogtreecommitdiff
path: root/src/Makefile.qttest.include
Commit message (Collapse)AuthorAgeFilesLines
* s/DOGE/DIS/gTomo Ueda2021-09-021-4/+4
|
* really s/doge/dis/g this timeTomo Ueda2021-09-021-16/+16
|
* Rename binaries to match DogecoinRoss Nicoll2019-03-251-16/+16
|
* Uses built-in byte swap if available (Apple) and if bswap_XX is undefined.Karl-Johan Alm2016-12-171-0/+3
| | | | Defers to pre-defined version if found (e.g. protobuf). For protobuf case, the definitions are identical and thus include order should not affect results.
* Add MIT license to MakefilesLuke Dashjr2016-09-211-0/+4
|
* [Qt] RPC-Console: support nested commands and simple value queriesJonas Schnelli2016-08-231-1/+5
| | | | | | | | | | | | | | | | Commands can be executed with bracket syntax, example: `getwalletinfo()`. Commands can be nested, example: `sendtoaddress(getnewaddress(), 10)`. Simple queries are possible: `listunspent()[0][txid]` Object values are accessed with a non-quoted string, example: [txid]. Fully backward compatible. `generate 101` is identical to `generate(101)` Result value queries indicated with `[]` require the new brackets syntax. Comma as argument separator is now also possible: `sendtoaddress,<address>,<amount>` Space as argument separator works also with the bracket syntax, example: `sendtoaddress(getnewaddress() 10) No dept limitation, complex commands are possible: `decoderawtransaction(getrawtransaction(getblock(getbestblockhash())[tx][0]))[vout][0][value]`
* Build: Consensus: Move consensus files from common to its own module/packageJorge Timón2015-12-081-1/+1
|
* build: Use fPIC rather than fPIE for qt objects.Cory Fields2015-11-091-1/+1
| | | | But only if qt was built with reduced relocations.
* build: Split hardening/fPIE options outCory Fields2015-11-091-1/+2
| | | | This allows for fPIE to be used selectively.
* [Univalue] add univalue over subtreeJonas Schnelli2015-10-011-1/+1
| | | | similar to secp256k1 include and compile univalue over a subtree
* Add ZeroMQ support. Notify blocks and transactions via ZeroMQJeff Garzik2015-09-161-0/+3
| | | | | | | | | Continues Johnathan Corgan's work. Publishing multipart messages Bugfix: Add missing zmq header includes Bugfix: Adjust build system to link ZeroMQ code for Qt binaries
* build: build-system changes for libeventWladimir J. van der Laan2015-09-021-1/+2
|
* build: make a distinction between static app ldflags and static lib ldflagsCory Fields2014-11-191-1/+1
| | | | | For windows builds, exe's are always static, but libs should still conform to --enabled-shared and --enable-static.
* Always build and link libsecp256k1Pieter Wuille2014-11-181-4/+1
|
* build: quit abusing LIBS for Windows builds.Cory Fields2014-10-131-1/+1
| | | | | | | | 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.
* build: fix qt test build when libprotobuf is in a non-standard pathCory Fields2014-10-101-1/+1
|
* build: add option for reducing exports (v2)Cory Fields2014-08-181-1/+1
| | | | | | | | | | | | 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.
* Revert "build: add option for reducing exports"Wladimir J. van der Laan2014-08-181-1/+1
| | | | | | | | | Revert #4663 for now. It still breaks the pulltester. This reverts commit 4975ae1722cd8af63eda2f02ef64a98091b6fb58. Conflicts: configure.ac
* build: add option for reducing exportsCory Fields2014-08-151-1/+1
| | | | | | | | 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.
* build: fix automake warnings about the use of INCLUDESCory Fields2014-08-151-1/+1
| | | | | | | | | | | 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 <[email protected]> Rebased-From: 909b347 c0e5dda
* Add "bitcoin-tx" command line utility and supporting modules.Jeff Garzik2014-07-291-1/+1
| | | | | | | | | | | | | 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.
* build: re-add AM_LDFLAGS where it's overriddenCory Fields2014-07-081-1/+1
| | | | using _LDFLAGS replaces AM_LDFLAGS rather than adding to it.
* secp256k1: Add build-side changes for libsecp256k1Cory Fields2014-07-011-0/+3
| | | | | | 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.
* Remove unnecessary dependencies for bitcoin-cliWladimir J. van der Laan2014-06-251-1/+1
| | | | | | | | | 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.
* crypto: create a separate lib for crypto functionsCory Fields2014-06-211-1/+1
| | | | | This lib has no dependencies on other bitcoin functionality. Attempting to use bitcoin headers will result in a failure to compile.
* build: quit abusing AM_CPPFLAGSCory Fields2014-06-051-6/+2
| | | | | | | | 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.
* build: avoid the use of top_ and abs_ dir pathsCory Fields2014-06-051-3/+3
| | | | Using them has the side effect of confusing the dependency-tracking logic.
* build: Switch to non-recursive makeCory Fields2014-06-051-0/+52
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.
generated by cgit v1.2.3 (git 2.25.1) at 2026-03-11 20:00:07 +0000