From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin-qt ready for merging
Date: Thu, 22 Sep 2011 16:11:16 -0400 [thread overview]
Message-ID: <201109221611.18163.luke@dashjr.org> (raw)
In-Reply-To: <CAJNQ0su7iRsQ2zPhXcd774TTqYzJGT+E9ss4D=6Ja3QSrpLdkw@mail.gmail.com>
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
next prev parent reply other threads:[~2011-09-22 20:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 14:20 John Smith
2011-08-31 15:07 ` Matt Corallo
2011-09-01 2:11 ` John Smith
2011-09-01 2:13 ` Luke-Jr
2011-09-01 2:32 ` John Smith
2011-09-22 20:11 ` Luke-Jr [this message]
2011-09-11 0:20 Alex Waters
2011-09-11 7:37 ` John Smith
[not found] ` <CAL0fb62M9=vKM4kag9rdQ=1bAbKdnoXD+7XR3eyKWY_Q4WEZXA@mail.gmail.com>
2011-09-11 9:54 ` John Smith
2011-09-11 17:12 ` Gavin Andresen
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=201109221611.18163.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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