Warning Warning Warning
Pre-alpha stuff! I'm using this client myself on the production network, and I haven't noticed any glitches, but remember: always backup your wallet. Testing on the testnet is recommended.
This has been implemented:
- qmake / QtCreator project (.pro)
- Compatibility with Linux (both GNOME and KDE), MacOSX and Windows
- All functionality of the original client, including taskbar icon/menu
- Tabbed interface
- Asks for confirmation before sending coins
- CSV export of transactions
- User friendly transaction list with status icons, and real-time filtering
- Show alternative icon when on testnet
- Progress bar on initial block download
This has to be done:
- Start at system start
- Internationalization (convert WX language files)
First, make sure that the required packages for Qt4 development of your distribution are installed, for Debian and Ubuntu these are:
apt-get install qt4-qmake libqt4-dev build-essential libboost-dev libboost-system-dev \ libboost-filesystem-dev libboost-program-options-dev libboost-thread-dev \ libssl-dev libdb4.8++-dev
then execute the following:
qmake make
Alternatively, install Qt Creator and open the bitcoin-qt.pro file.
An executable named bitcoin-qt will be built.
Windows build instructions:
- Download the QT Windows SDK and install it. You don't need the Symbian stuff, just the desktop Qt.
- Download and extract the dependencies archive [1], or compile openssl, boost and dbcxx yourself.
- Copy the contents of the folder "deps" to "X:QtSDKmingw", replace X:with the location where you installed the Qt SDK. Make sure that the contents of "deps/include" end up in the current "include" directory and such.
- Open the .pro file in QT creator and build as normal (ctrl-B)
[1] | PGP signature: http://download.visucore.com/bitcoin/qtgui_deps_1.zip.sig (signed with RSA key ID 610945D0) |
A warning for people using the static binary version of Bitcoin on a Linux/UNIX-ish system (tl;dr: Berkely DB databases are not forward compatible).
The static binary version of Bitcoin is linked against libdb4.7 or libdb4.8 (see also this Debian issue).
Now the nasty thing is that databases from 5.X are not compatible with 4.X.
If the globally installed development package of Berkely DB installed on your system is 5.X, any source you build yourself will be linked against that. The first time you run with a 5.X version the database will be upgraded, and 4.X cannot open the new format. This means that you cannot go back to the old statically linked version without significant hassle!