Skip to content
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

Add NATIVE_WINDOWS #1940

Merged
merged 1 commit into from
Dec 12, 2012
Merged

Add NATIVE_WINDOWS #1940

merged 1 commit into from
Dec 12, 2012

Conversation

grimd34th
Copy link
Contributor

With a change of libs, and specifying NATIVE_WINDOWS as TARGET_OS it should compile libleveldb.a and libmemenv.a just fine, it did for me and Diapolo when testing.

With a change of libs, and specifying NATIVE_WINDOWS as TARGET_OS it should compile libleveldb.a and libmemenv.a just fine, it did for me and Diapolo when testing.
@BitcoinPullTester
Copy link

Automatic sanity-testing: FAILED BUILD/TEST, see http://jenkins.bluematt.me/pull-tester/46936f343c5f9740e1ad8e0defeced7861c1a35a for binaries and test log.

This could happen for one of several reasons:

  1. It chanages paths in makefile.linux-mingw or otherwise changes build scripts in a way that made them incompatible with the automated testing scripts
  2. It does not build on either Linux i386 or Win32 (via MinGW cross compile)
  3. The test suite fails on either Linux i386 or Win32
  4. The block test-cases failed (lookup the first bNN identifier which failed in https://github.com/TheBlueMatt/test-scripts/blob/master/FullBlockTestGenerator.java)

@Diapolo
Copy link

Diapolo commented Oct 30, 2012

It would be nice if the one, who did the Windows port could comment. Problem is I dunno, who it was...

@Diapolo
Copy link

Diapolo commented Nov 11, 2012

It would be even nicer, if that Boost stuff could be auto-detected, but I dunno how that could be achieved here. At least the uses version stuff here should match that from bitcoin-qt.pro, so I propose -mgw44-mt-s-1_50!

https://github.com/bitcoin/bitcoin/blob/master/bitcoin-qt.pro#L320

That patch is clearly for users building LevelDB directly on Windows, which currently doesn't work with Qt Creator as (for MinGW) you need to build LevelDB separately via the MinGW shell.

@sipa
Copy link
Member

sipa commented Nov 11, 2012

Or even nicer if the Windows port didn't depend on boost...

@grimd34th
Copy link
Contributor Author

Diapolo, i tried to make it like the https://github.com/bitcoin/bitcoin/blob/master/src/makefile.mingw#L18

@gavinandresen
Copy link
Contributor

Merging on the assumption "better behavior than we had before"

gavinandresen added a commit that referenced this pull request Dec 12, 2012
@gavinandresen gavinandresen merged commit 5bd5d6c into bitcoin:master Dec 12, 2012
laudney pushed a commit to reddcoin-project/reddcoin-3.10 that referenced this pull request Mar 19, 2014
KolbyML pushed a commit to KolbyML/bitcoin that referenced this pull request Dec 5, 2020
…ork connection and validations.

a3c4d2d New constant MAX_STANDARD_SHIELDED_TX_SIZE defined for sapling txes standard-ness checks inside IsStandardTx. (furszy)
31a8fed TransactionBuilder: Do not set the binding signature if there is no shielded spends/outs. (furszy)
ef47c57 Validation: Connecting Sapling ContextualCheckTransaction. (furszy)
bfa4db4 Sapling transaction fixed fee check. (furszy)
ef6c419 Add HaveShieldedRequirements checks in mempool, connectBlock and checkTxInputs (furszy)
880d289 validation: sapling merkle tree and view state update connection. (furszy)
d6bcb06 Sapling CheckTransaction connection. (furszy)
74cbe90 Sapling validation, CheckTransaction implemented. (furszy)
89a469f Solver return false for empty scripts. (furszy)

Pull request description:

  Hopefully the last decouple from bitcoin#1798.

  Focused on introducing network flow connection and validations for shielded transactions (primitives and contextual checks), coins cache nullifier and anchor and a test case covering the invalid paths.

  This work can be verified running 1798 functional tests suite. `sapling_wallet_nullifiers.py`, `sapling_wallet.py`, `sapling_wallet_anchorfork.py` , `sapling_key_import_export.py` are all running on top of this work, creating shielded txs, checking balances and generating blocks.

  -- A future to do in the area is the mempool validations (nullifiers) connection (stated in 1798 but a little bit of redundancy here doesn't hurt) and continue adding more test coverage for the validation area. Plus, discuss the fee topic further on its own PR, can be dynamic and not fixed as is now. --

  #### Commits coming from 1798:

  * PR decoupled from 1798, focused on introducing Sapling transaction network validations.
  * TransactionBuilder: Do not set the binding signature if there is no shielded spends/outs. —> 096b0ed
  * Validation: Connecting Sapling ContextualCheckTransaction. —> b37998c
  * Sapling transaction fixed fee check. —> cda336e
  * Add HaveShieldedRequirements checks in mempool, connectBlock and checkTxInputs —> 3dbd319
  * validation: sapling merkle tree and view state update connection. —> 382a99b
  * Sapling CheckTransaction connection. —> 3b40c6e
  * Sapling validation, CheckTransaction implemented. —> 7fd17ee
  * Solver return false for empty scripts. —> 3622a0d

ACKs for top commit:
  random-zebra:
    re-utACK a3c4d2d
  Fuzzbawls:
    utACK a3c4d2d

Tree-SHA512: 000127b623f3f1383fc1996cb811ba0e977ad6b2ada3fe8da80e2cbe685884aa7708ad906165c916e86f5d1a3676a54d6b1a0f44f9613a2ab1dfaace170f6fd3
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants