From: Mark Visser <mjmvisser@gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Roadmap for autotools / Qt gui merge [Mac update]
Date: Sun, 19 Jun 2011 22:34:03 -0400 [thread overview]
Message-ID: <3562E09F-A129-4D97-9624-6002544C7430@gmail.com> (raw)
In-Reply-To: <20110619003048.GA26366@ulyssis.org>
Hi everyone,
I spent some time today with the bitcoin-qt client and autotools on mac. The qt client builds and runs with a few small changes (mostly just #including boost/filesystem/operations.hpp in a few places).
Autotools + qt will take a bit longer. I've got something *almost* working, but I won't have a chance to finish it for the rest of the week. I'll push the changes to github tomorrow (Monday) so anyone else can take a crack at it if they so wish.
cheers,
-Mark
On 2011-06-18, at 8:30 PM, Pieter Wuille wrote:
> On Fri, Jun 17, 2011 at 06:42:30AM +0000, John Smith wrote:
>> Hello,
>>
>> I think my Qt GUI is pretty much ready for merging. I've been using it for a
>> while and all functionality works.
>>
>> What is the current roadmap for including the autotools build system, so
>> that it will be possible to support multiple GUIs? 0.4.0?
>
> The consensus seems to be to merge autotools and qtgui. However, autotools is
> apparently not tested (enough) on native windows and osx platforms.
>
> Anyone on this list with either development environnement, and willingness
> to test?
>
> --
> Pieter
>
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
next prev parent reply other threads:[~2011-06-20 2:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 6:42 [Bitcoin-development] Roadmap for autotools / Qt gui merge John Smith
2011-06-17 7:05 ` Brendan Molloy
2011-06-17 10:31 ` Pieter Wuille
2011-06-17 13:29 ` Luke-Jr
2011-06-17 14:10 ` Douglas Huff
2011-06-17 16:27 ` Gavin Andresen
2011-06-17 20:37 ` Luke-Jr
2011-06-17 22:59 ` Jeff Garzik
2011-06-19 0:30 ` Pieter Wuille
2011-06-20 2:34 ` Mark Visser [this message]
2011-06-22 14:18 ` Pieter Wuille
2011-06-19 1:37 ` Luke-Jr
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=3562E09F-A129-4D97-9624-6002544C7430@gmail.com \
--to=mjmvisser@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=pieter.wuille@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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