-
Notifications
You must be signed in to change notification settings - Fork 36.3k
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
Update NSIS Installer file to support the new directory structure. #249
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jgarzik
pushed a commit
that referenced
this pull request
May 24, 2011
Update NSIS Installer file to support the new directory structure.
dexX7
pushed a commit
to dexX7/bitcoin
that referenced
this pull request
Dec 19, 2014
Couple of files for PR247 were untracked and didn't get committed
kleetus
pushed a commit
to kleetus/bitcoin
that referenced
this pull request
Feb 5, 2016
Changes are: * Update version number to 1.18 * Replace the basic fprintf call with a call to fwrite in order to work around the apparent compiler optimization/rewrite failure that we are seeing with the new toolchain/iOS SDKs provided with Xcode6 and iOS8. * Fix ALL the header guards. * Createed a README.md with the LevelDB project description. * A new CONTRIBUTING file. * Don't implicitly convert uint64_t to size_t or int. Either preserve it as uint64_t, or explicitly cast. This fixes MSVC warnings about possible value truncation when compiling this code in Chromium. * Added a DumpFile() library function that encapsulates the guts of the "leveldbutil dump" command. This will allow clients to dump data to their log files instead of stdout. It will also allow clients to supply their own environment. * leveldb: Remove unused function 'ConsumeChar'. * leveldbutil: Remove unused member variables from WriteBatchItemPrinter. * OpenBSD, NetBSD and DragonflyBSD have _LITTLE_ENDIAN, so define PLATFORM_IS_LITTLE_ENDIAN like on FreeBSD. This fixes: * issue bitcoin#143 * issue bitcoin#198 * issue bitcoin#249 * Switch from <cstdatomic> to <atomic>. The former never made it into the standard and doesn't exist in modern gcc versions at all. The later contains everything that leveldb was using from the former. This problem was noticed when porting to Portable Native Client where no memory barrier is defined. The fact that <cstdatomic> is missing normally goes unnoticed since memory barriers are defined for most architectures. * Make Hash() treat its input as unsigned. Before this change LevelDB files from platforms with different signedness of char were not compatible. This change fixes: issue bitcoin#243 * Verify checksums of index/meta/filter blocks when paranoid_checks set. * Invoke all tools for iOS with xcrun. (This was causing problems with the new XCode 5.1.1 image on pulse.) * include <sys/stat.h> only once, and fix the following linter warning: "Found C system header after C++ system header" * When encountering a corrupted table file, return Status::Corruption instead of Status::InvalidArgument. * Support cygwin as build platform, patch is from https://code.google.com/p/leveldb/issues/detail?id=188 * Fix typo, merge patch from https://code.google.com/p/leveldb/issues/detail?id=159 * Fix typos and comments, and address the following two issues: * issue bitcoin#166 * issue bitcoin#241 * Add missing db synchronize after "fillseq" in the benchmark. * Removed unused variable in SeekRandom: value (issue bitcoin#201)
destenson
pushed a commit
to destenson/bitcoin--bitcoin
that referenced
this pull request
Nov 18, 2017
Github-Pull: bitcoin#249 Rebased-From: 7405e31
classesjack
pushed a commit
to classesjack/bitcoin
that referenced
this pull request
Jan 2, 2018
create getTransactionReceipt rpc call (Qtum Core / QTUMCORE-81)
Losangelosgenetics
pushed a commit
to Losangelosgenetics/bitcoin
that referenced
this pull request
Mar 12, 2020
cryptapus
pushed a commit
to cryptapus/bitcoin
that referenced
this pull request
May 3, 2021
4cf815e Add release notes entry for encodings. (Daniel Kraft) 810bc13 Support -name/valueencoding for namecoin-tx. (Daniel Kraft) 20ab39a Handle encodings on the output side. (Daniel Kraft) 482c30e Explicitly use UTF-8 for name_filter regexp check. (Daniel Kraft) ee7fba9 Introduce EncodeNameForMessage for logs / errors. (Daniel Kraft) 80f8ba0 Move names/encoding library to common lib. (Daniel Kraft) 0688f01 Remove ValtypeFromString. (Daniel Kraft) 9367b48 Use configured encoding for "input" names/values. (Daniel Kraft) 7e364eb Add -nameencoding / -valueencoding options. (Daniel Kraft) b6b8483 Add new names/encoding source files. (Daniel Kraft) 0a1c72e Expose univalue's UTF-8 validation logic. (Daniel Kraft) Pull request description: This implements the main part of the proposal in bitcoin#246: New `-nameencoding` and `-valueencoding` options are added, with the possible values of `ascii`, `utf8` and `hex`. They specify in which encoding name and value data is expected in RPC arguments and returned in JSON fields. This fixes a long-standing issue Namecoin had with binary data that was invalid UTF-8 (as well as adding proper support for real binary data in the RPC interface). As a consequence, this likely resolves (or is at least a big part of the solution of) bitcoin#152 and bitcoin#170. Still missing for a full solution of bitcoin#246 is the possibility to specify per-RPC encodings in an `options` RPC argument. For now, the encodings can only be set for the full process at startup time through the config options. Tree-SHA512: b221c3ccf421517be3419aec568e02475c2562fa1e99a70b7c53332ce343dc78a537285183262b270fb676f7c39cf16a9e58cb8160e2e4653211d0daa77e0437
rajarshimaitra
pushed a commit
to rajarshimaitra/bitcoin
that referenced
this pull request
Aug 5, 2021
throught for through Co-authored-by: Rene Pickhardt <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.