Sure.
Because I trust you, I'll send the whole bounty to them already. See PM for transaction id.
Topic: Autotools Qt5 support (200 mBTC bounty) (Read 1063 times)
The final PR for this is in. See: https://github.com/bitcoin/bitcoin/pull/3346
Ready for final review and testing. It's merge-ready barring any new reports of build problems.
Since you said you're happy to send along the bounty (when merged), I have a proposal for you:
As mentioned above, I'm not ok with keeping it because IMO it was a regression that I introduced anyway. Instead, I'd like to see it donated to Sean's Outpost (http://seansoutpost.com).
However, given that they are working hard to help families for Christmas, I'd really hoped to have this taken care in time to contribute.
Could I persuade you to go ahead and send along half to Sean's Outpost, and the rest after merge? I obviously have every intention of getting this into master.
Ready for final review and testing. It's merge-ready barring any new reports of build problems.
Since you said you're happy to send along the bounty (when merged), I have a proposal for you:
As mentioned above, I'm not ok with keeping it because IMO it was a regression that I introduced anyway. Instead, I'd like to see it donated to Sean's Outpost (http://seansoutpost.com).
However, given that they are working hard to help families for Christmas, I'd really hoped to have this taken care in time to contribute.
Could I persuade you to go ahead and send along half to Sean's Outpost, and the rest after merge? I obviously have every intention of getting this into master.
Though my idea behind posting a bounty for a relatively straightforward task is to incite some new people to development on the reference client.
I may do this again for some other things.
I may do this again for some other things.
Okay, that's up to you, I'm still happy to send you the bounty if you do 
This is on my todo list (I did the initial autotools port).
Because it's a regression, I consider this part of the port that was not completed. Thus, no bounty needed, I'll take care of it very soon. I have most of it done in a branch somewhere, just need to finish up my current project first.
Because it's a regression, I consider this part of the port that was not completed. Thus, no bounty needed, I'll take care of it very soon. I have most of it done in a branch somewhere, just need to finish up my current project first.
Looking for an autotools wizard to add Qt5 support to the GNU autotools build system of the bitcoin reference client (https://github.com/bitcoin/bitcoin).
Qt5 support was lost when switching from qmake to autotools.
* Qt4 must remain supported
* Which one to use should be auto-detected
* If both Qt4 and Qt5 are installed Qt5 should be used by default
* It should be possible to choose which one to use using a configure option.
Bounty: 200 mBTC, will be paid by me when your change is merged.
Please post here if you start working on this, so that no duplicate work is done.
If you have further questions let me know.
Note: this only concerns build system work, the underlying code base already supports Qt5 (and if there are issues with that, you do not have to fix those to claim the bounty)
Qt5 support was lost when switching from qmake to autotools.
* Qt4 must remain supported
* Which one to use should be auto-detected
* If both Qt4 and Qt5 are installed Qt5 should be used by default
* It should be possible to choose which one to use using a configure option.
Bounty: 200 mBTC, will be paid by me when your change is merged.
Please post here if you start working on this, so that no duplicate work is done.
If you have further questions let me know.
Note: this only concerns build system work, the underlying code base already supports Qt5 (and if there are issues with that, you do not have to fix those to claim the bounty)
Jump to: