-
Notifications
You must be signed in to change notification settings - Fork 35.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimize header dependencies; improve Makefile dependency graph #226
Conversation
rpc.cpp: In function ‘void ThreadRPCServer2(void*)’: |
Thanks - I didn't see that with g++4.3/amd64 - could you please tell me what platform and compiler you're using? |
OK, I fixed the issue. |
ui.cpp: In member function ‘virtual void CMainFrame::OnClose(wxCloseEvent&)’: |
OK, issue should be fixed for DGUI now as well. |
ui.cpp: In function ‘void SetStartOnSystemStartup(bool)’: |
I've rebased the above fixes for further review. |
All patches look OK. I would elide the *.d commit, because we'll be doing that via GNU autotools as soon as jaromil's branch is pulled (post 0.3.22 release). |
.d commit elided. |
ACK- should be pulled for the release-after-0.3.23 |
Optimize header dependencies; improve Makefile dependency graph
isTransactionTypeAllowed bypass for property = 0
4d06a8d Remove checkpoint tests for old hashing process (zathras-crypto) 755abb5 Remove second tally lock (thanks @dexX7) (zathras-crypto) 959264f Break out consensus string generation (thanks @dexX7) (zathras-crypto) 1a8ad4f Update checkpoints to reflect new consensus hashing process (zathras-crypto) 18669b4 Add current issuer address for properties to consensus hash (zathras-crypto) 7b7fd42 Update checkpoints for new consensus hash algo (zathras-crypto) 5af9547 Remove reserved amounts from DEx sell data added to consensus hash (zathras-crypto) a902c4d Remove unused GetTallyPropertyTotal() (zathras-crypto) d51edb2 Switch properties to next available instead of token counts (thanks @dexX7) (zathras-crypto) 66561dd Tidy up consensus hashing changes (zathras-crypto) af151cb Sort DEx accepts by matching txid then buyer for consensus hashing (zathras-crypto) 95e92ea Order DEx offers and MetaDEx trades by txid in consensus hash (zathras-crypto) a98132a Order crowd data in consensus hash by property id (zathras-crypto) 6cbd79d Add DEx accept to consensus hash (zathras-crypto) f726c50 Add property id and total amount of tokens to consensus hash (zathras-crypto) 86a6176 Add crowdsale data to consensus hash (zathras-crypto) ffe6206 Add MetaDEx trade data to consensus hash (zathras-crypto) abeba7a Allow generating consensus hashes after each Omni transaction (zathras-crypto) fdee9d5 Fix format specifiers for DEx data in consensus hash (zathras-crypto) f394ed1 Add DEx offers to consensus hash calculations (zathras-crypto) 1eafd66 Extract GetConsensusHash() into consensushash.h/cpp (zathras-crypto)
Increase OP_ RETURN relay to 80 bytes
Release Branch - Fix maxblocksinflight
Remove explicit check for -nodebug arg
d189372 Explicitly handle name outputs for listunspent. (Daniel Kraft) 80268a7 Make name-script-to-JSON publicly accessible. (Daniel Kraft) Pull request description: Previously, `listunspent` did not explicitly handle name outputs - and as a consequence, they were just shown mixed in with (and undistinguishable from) the currency outputs. This adds explicit handling: * Any *expired* name outputs are always excluded, as they are unspendable. * Other name outputs are included in the results only if the new `includeNames` RPC option, which is off by default, is set. * If name outputs are included in the result, then they are marked by a `nameOp` field equivalent to that of `decoderawtransaction`. This implements namecoin/namecoin-core#192. Tree-SHA512: ab0adb465ca71127688cb05b9cf41685b349b821bc951916967af980baeb18afd6fdf42bd429139fa30868f023166bac7c251ddbcfdf83cbb2d4e889c6afe492
lose instead of loose
This patch set includes the following changes:
These changes improve bitcoin's development environment. Previously changing any header file caused a global recompile. With these changes, only those files that directly depend on a changed header file will require recompilation.