Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1R6pcW-0001Np-5m for bitcoin-development@lists.sourceforge.net; Thu, 22 Sep 2011 20:11:44 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1R6pcV-0000FZ-BN for bitcoin-development@lists.sourceforge.net; Thu, 22 Sep 2011 20:11:44 +0000 Received: from ishibashi.localnet (fl-184-4-160-40.dhcp.embarqhsd.net [184.4.160.40]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id CC6FE560766; Thu, 22 Sep 2011 20:11:37 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Thu, 22 Sep 2011 16:11:16 -0400 User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo; KDE/4.6.5; x86_64; ; ) References: In-Reply-To: X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583 X-PGP-Key-ID: 665FC11DD53E9583 X-PGP-Keyserver: x-hkp://subkeys.pgp.net MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201109221611.18163.luke@dashjr.org> X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1R6pcV-0000FZ-BN Subject: Re: [Bitcoin-development] Bitcoin-qt ready for merging 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, 22 Sep 2011 20:11:44 -0000 Various issues with bitcoin-qt's qmake build system still... Regressions remaining on bitcoin-qt branch: - Building without DBus still tries to use dbus symbols (and fails linking) - No way to disable SSL support for JSON-RPC - UPnP is no longer built/enabled by default These weren't quite working in the old makefiles either, but it was a lot easier to workaround with DEBUGFLAGS: - No way to specify include path or library names for bdb and boost (won't build, since bdb C++ includes aren't default on many OS) - No way to build with out-of-tree/system cryptopp or json