From: Gavin Andresen <gavinandresen@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] 0.5 release updated
Date: Fri, 28 Oct 2011 14:33:44 -0400 [thread overview]
Message-ID: <CABsx9T3Csb5qKTeEWoA_1_e0s0OnXFjxVpw2EV0RP+6hATeDrA@mail.gmail.com> (raw)
Quick update on why there is no final 0.5 release out yet:
Short answer: because I'm really paranoid about bitcoin binary builds,
and the switch to Qt means a change in the way the builds are done.
Long answer:
Linux builds should be all set; the 'gitian' trusted build process works nicely.
Windows builds are being difficult; we need a gcc expert to help debug
the 'gitian' cross-compile (see
https://github.com/bitcoin/bitcoin/pull/587 ).
Unless somebody steps forward and says "I'll support compiling
bitcoin-qt/bitcoind with Visual Studio) I'm going to remove
src/makefile.vc and make sure the readmes say that only the mingw
toolchain is supported.
Mac builds were slightly broken for the 0.4 release (they don't run on
OSX 10.5-- you need 10.6 or greater). I'm "recompiling the world" to
hopefully fix that, and hope to have mac binaries available soon (let
me know if you can help test, especially if you have a 32-bit Intel
mac running 10.5).
On my wish list for builds (anybody want to volunteer?):
I think it'd be spiffy to have a .pro file to compile bitcoind;
maintaining N different makefiles is annoying and error-prone.
--
--
Gavin Andresen
next reply other threads:[~2011-10-28 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 18:33 Gavin Andresen [this message]
2011-10-28 23:56 ` Luke-Jr
2011-10-29 8:09 ` John Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABsx9T3Csb5qKTeEWoA_1_e0s0OnXFjxVpw2EV0RP+6hATeDrA@mail.gmail.com \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox