slackcoder/bitcoin - Bitcoin Code integration/staging tree

Age	Commit message (Collapse)	Author
2018-06-14	Add "export LC_ALL=C" to all shell scripts	practicalswift

2017-10-18	Add error handling: exit if cd fails	practicalswift

2017-05-17	Merge #7522: Bugfix: Only use git for build info if the repository is ↵	Wladimir J. van der Laan
	actually the right one ed1fcdc Bugfix: Detect genbuild.sh in repo correctly (Luke Dashjr) e98e3dd Bugfix: Only use git for build info if the repository is actually the right one (Luke Dashjr) Tree-SHA512: 510d7ec8cfeff4e8e0c7ac53631eb32c7acaada7017e7f8cc2e6f60d86afe1cd131870582e01022f961c85a783a130bcb8fef971f8b110070c9c02afda020726
2016-12-29	Bugfix: Detect genbuild.sh in repo correctly	Luke Dashjr

2016-09-21	Add MIT license to autogen.sh and share/genbuild.sh	Luke Dashjr

2016-08-09	Merge tag 'branch-0.13' into bugfix_gitdir	Luke Dashjr

2016-06-09	build: Get rid of `CLIENT_DATE`	Wladimir J. van der Laan
	Putting the build date in the executable is a practice that has no place in these days, now that deterministic building is increasingly common. Continues #7732 which did this for the GUI.
2016-02-12	Bugfix: Only use git for build info if the repository is actually the right one	Luke Dashjr
	Also adds ability to disable check with BITCOIN_GENBUILD_NO_GIT=1 in the environment
2015-05-04	build: if there's no recent git tag, don't spew error messages	Cory Fields

2014-11-04	build: Fix "too many arguments" error	Francis GASCHET
	Closes #5141
2014-09-19	build: fix release name strings for gitian builds	Cory Fields
	When building from a distdir as gitian does, checking for the .git dir is not reliable. Instead, ask git if we're in a repo.
2014-05-09	build: fix: remove error output	harry
	while git not found in path, error is output to console.
2014-04-15	VERSION obtained from source instead of the previous git tag.	Warren Togami
	Drawback: The version string is no longer a valid git identifier. For this reason the 'g' short hash prefix has been removed. Exception: When building directly from a tag this behaves exactly like the previous behavior. This allows formatting release versions with precision i.e. v0.9.2 This also allows arbitrary topicbranch names i.e. v0.9.1-glibc-compat
2014-01-30	Fix build time when building from tarball (now really)	Wladimir J. van der Laan
	Don't define BUILD_DATE at all when no git version information is available. `version.cpp` will then define it for us correctly to the last commit date. This has been fixed and broken many times over 0.9 history (21cc8bd, ef1e984), please don't touch this code unless you plan on testing all possible scenarios including gitian builds. Fixes #3570.
2013-11-21	Provide build time when building from tarball:	Dmitry Smirnov
	When building from tarball (i.g. not from git source tree or when git is not available) `genbuild.sh` write undefined $TIME to "build/build.h". Even worse, when TIME is set in the environment then its value is written instead of a date. For me this change fixed FTBFS which I got because I had TIME enviroment variable set with format for time(1) utility.
2013-09-05	autotools: switch to autotools buildsystem	Cory Fields

2012-04-10	Build identification strings	Pieter Wuille
	All client version information is moved to version.cpp, which optionally (-DHAVE_BUILD_INFO) includes build.h. build.h is automatically generated on supporting platforms via contrib/genbuild.sh, using git describe. The git export-subst attribute is used to put the commit id statically in version.cpp inside generated archives, and this value is used if no build.h is present. The gitian descriptors are modified to use git archive instead of a copy, to create the src/ directory in the output. This way, src/src/version.cpp will contain the static commit id. To prevent gitian builds from getting the "-dirty" marker in their git-describe generated identifiers, no touching of files or running sed on the makefile is performed anymore. This does not seem to influence determinism.