From: Wladimir <laanwj@gmail•com>
To: kristovatlas@gmail•com
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Development Roadmap of Bitcoin Core 0.9.2
Date: Thu, 24 Apr 2014 10:07:22 +0200 [thread overview]
Message-ID: <CA+s+GJAtGRQWKw9tL=CdN48qa7LPKCfdzisyKj7x6YmZ+5M+FQ@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJDY6c2-fjbL=JcrF3umM4ji8Y5j5ppxX_mAzZdTh1_QRw@mail.gmail.com>
On Thu, Apr 24, 2014 at 10:02 AM, Wladimir <laanwj@gmail•com> wrote:
> On Thu, Apr 24, 2014 at 12:28 AM, Gregory Maxwell <gmaxwell@gmail•com> wrote:
>> On Wed, Apr 23, 2014 at 1:39 PM, Warren Togami Jr. <wtogami@gmail•com> wrote:
>>> If you are
> > Another option: Instead of statically building it'd be easy enough to
> build against the 4.6 Qt headers instead without even swapping the
> library. Qt is, after all, forward-compatible - between the 4.x
> versions. This will lose some GUI features but if compatibility is
> more important here that's a choice that can be made.
Are you sure this is Qt 4.6 at all? Not Qt 4.7?
I'd expect *much* more symbols if this was a Qt 4.8 versus 4.6
conflict. Qt 4.7 introduced a lot of new things (see all the
occurences of #if QT_VERSION >= 0x040700 - things like
setPlaceHolderText would be expected to pop up too), but 4.8 did not.
Can you check?
Wladimir
next prev parent reply other threads:[~2014-04-24 8:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 13:30 Warren Togami Jr.
2014-04-22 14:05 ` Wladimir
2014-04-23 20:05 ` Kristov Atlas
2014-04-23 20:28 ` Wladimir
2014-04-23 20:39 ` Warren Togami Jr.
2014-04-23 20:52 ` Kristov Atlas
2014-04-23 22:28 ` Gregory Maxwell
2014-04-24 1:56 ` Kristov Atlas
2014-04-24 8:02 ` Wladimir
2014-04-24 8:07 ` Wladimir [this message]
2014-04-24 8:15 ` Warren Togami Jr.
2014-04-24 8:25 ` Wladimir
2014-04-24 12:18 ` Wladimir
2014-04-25 20:09 ` Kristov Atlas
2014-04-25 20:47 ` Wladimir
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='CA+s+GJAtGRQWKw9tL=CdN48qa7LPKCfdzisyKj7x6YmZ+5M+FQ@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=kristovatlas@gmail$(echo .)com \
/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