Update doc/build-unix.txt #1755

Merged
merged 1 commit into from Sep 11, 2012

Projects

None yet

7 participants

@osmosis79

how to build on ubuntu 12.04

@Diapolo Diapolo commented on the diff Aug 30, 2012
doc/build-unix.txt
-sudo apt-get install libqrencode-dev
-
-If using Boost 1.37, append -mt to the boost libraries in the makefile.
+Build requirements:
+ sudo apt-get install build-essential
+ sudo apt-get install libssl-dev
+
+for Ubuntu 12.04:
+ sudo apt-get install libdb5.1-dev
+ sudo apt-get install libdb5.1++-dev
+ sudo apt-get install libboost-all-dev
+
+for other Ubuntu & Debian:
+ sudo apt-get install libdb4.8-dev
+ sudo apt-get install libdb4.8++-dev
+ sudo apt-get install libboost1.37-dev
@Diapolo
Diapolo Aug 30, 2012

I'm rather sure it would be better to not use such an old Boost version, but if we use that for the Linux build this just reflects it ;).

@osmosis79
osmosis79 Aug 30, 2012

if thats the case, better update line 59 too. It specifies "Versions used in this release: Boost 1.37". I tested on ubuntu 12.04, so added the name of the newer package accordingly.

@laanwj
Bitcoin member

Is this only for the bitcoind build? Or also bitcoin-qt? Because it includes libqrencode et al which are only used by the GUI.
In that case you also need to add qt4-qmake libqt4-dev

@osmosis79

thats a good point. Yes, strangely bitcoind does require libqrencode...unless the disable flag is specified. I havent built bitcoin-qt.

@laanwj
Bitcoin member

You must be wrong. I cannot find any mention of even the word 'qr' in makefile.unix.

@osmosis79

scratch that... I meant libminiupnpc-dev. No, libqrencode is not required. Ill go ahead and add the qt libs to the list.

@osmosis79

ok, removed libqrencode from build-unix.txt, and left other qt libs out. QR instructions are in readme-qt.rst

@gmaxwell
Bitcoin member

Hm. Is it wise to add instructions that will have people building binaries which will write wallets the project builds can't read?

@laanwj
Bitcoin member
@BitcoinPullTester

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/9386e61695cab47d8cd7037489c2cc86ce5ff864 for binaries and test log.

@osmosis79

I agree, there is no other supported way to build on ubuntu 12.04.
For 'wallets the project builds can't read', do we fail sanely?

@TheBlueMatt TheBlueMatt and 1 other commented on an outdated diff Aug 31, 2012
doc/build-unix.txt
@@ -61,15 +54,23 @@ Versions used in this release:
Dependency Build Instructions: Ubuntu & Debian
----------------------------------------------
-sudo apt-get install build-essential
-sudo apt-get install libssl-dev
-sudo apt-get install libdb4.8-dev
-sudo apt-get install libdb4.8++-dev
- Boost 1.40+: sudo apt-get install libboost-all-dev
- or Boost 1.37: sudo apt-get install libboost1.37-dev
-sudo apt-get install libqrencode-dev
-
-If using Boost 1.37, append -mt to the boost libraries in the makefile.
+Build requirements:
+ sudo apt-get install build-essential
+ sudo apt-get install libssl-dev
+
+for Ubuntu 12.04:
+ sudo apt-get install libdb5.1-dev
@TheBlueMatt
TheBlueMatt Aug 31, 2012

NACK, if anything, tell them to add the ppa and use db4.*++ from there.

@laanwj
laanwj Sep 1, 2012

Maybe add a warning that it is recommended to build with db 4.x, because wallet compatibility with the binary builds will be lost when converting to db 5.x. If you don't care about compatibility there is no reason to go through the extra trouble of finding a db4.x++ package.

@laanwj
Bitcoin member

This change seems to be accepted apart from the dbc++ version change. If you remove that change for now (and squash into one commit), we can at least merge this.

@osmosis79

added info for PPA and db compatibility. squashed changes to single commit. should be good to go.

@laanwj laanwj merged commit 8b1eb56 into bitcoin:master Sep 11, 2012
@BitcoinPullTester

Automatic sanity-testing: FAILED MERGE, see http://jenkins.bluematt.me/pull-tester/224222746698db200d4c47e1611219f25fc5aa71 for test log.

This pull does not merge cleanly onto current master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment