[Bitcoin-development] 0.5 release updated

[Bitcoin-development] 0.5 release updated

[Gavin Andresen]

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

Re: [Bitcoin-development] 0.5 release updated

[Luke-Jr]

On Friday, October 28, 2011 2:33:44 PM Gavin Andresen wrote:
> 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 ).

This is an Ubuntu issue. Can't gitian use something else?

> I think it'd be spiffy to have a .pro file to compile bitcoind;
> maintaining N different makefiles is annoying and error-prone.

Better would be a GUI=0/1 option to the bitcoin-qt.pro until a nicer (ideally 
automake/autoconf) system is implemented...

Re: [Bitcoin-development] 0.5 release updated

[John Smith]

[-- Attachment #1: Type: text/plain, Size: 534 bytes --]

> Better would be a GUI=0/1 option to the bitcoin-qt.pro until a nicer
> (ideally
> automake/autoconf) system is implemented...
>

Are you sure you want to require qmake for the daemon build?

I agree having a unified build system would be nice, but qmake doesn't add
anything for non-qt software. Better to stick with a makefile.

If the goal is 'making it easier for the user' maybe it'd be best to make a
bash script that wraps both, that builds the daemon if possible, and the UI
if possible, and converts command line flags.

JS

[-- Attachment #2: Type: text/html, Size: 798 bytes --]