From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WdEgq-00085e-G3 for bitcoin-development@lists.sourceforge.net; Thu, 24 Apr 2014 08:07:28 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.178 as permitted sender) client-ip=209.85.223.178; envelope-from=laanwj@gmail.com; helo=mail-ie0-f178.google.com; Received: from mail-ie0-f178.google.com ([209.85.223.178]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WdEgp-0001Tt-PK for bitcoin-development@lists.sourceforge.net; Thu, 24 Apr 2014 08:07:28 +0000 Received: by mail-ie0-f178.google.com with SMTP id lx4so2071328iec.9 for ; Thu, 24 Apr 2014 01:07:22 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.42.67.130 with SMTP id t2mr295560ici.17.1398326842539; Thu, 24 Apr 2014 01:07:22 -0700 (PDT) Received: by 10.64.22.168 with HTTP; Thu, 24 Apr 2014 01:07:22 -0700 (PDT) In-Reply-To: References: <53581D1D.1000709@gmail.com> Date: Thu, 24 Apr 2014 10:07:22 +0200 Message-ID: From: Wladimir To: kristovatlas@gmail.com Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WdEgp-0001Tt-PK Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Development Roadmap of Bitcoin Core 0.9.2 X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Apr 2014 08:07:28 -0000 On Thu, Apr 24, 2014 at 10:02 AM, Wladimir wrote: > On Thu, Apr 24, 2014 at 12:28 AM, Gregory Maxwell wrote: >> On Wed, Apr 23, 2014 at 1:39 PM, Warren Togami Jr. 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