Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <witchspace81@gmail.com>) id 1RK3yb-0002uA-7T
	for bitcoin-development@lists.sourceforge.net;
	Sat, 29 Oct 2011 08:09:13 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.161.175 as permitted sender)
	client-ip=209.85.161.175; envelope-from=witchspace81@gmail.com;
	helo=mail-gx0-f175.google.com; 
Received: from mail-gx0-f175.google.com ([209.85.161.175])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
	(Exim 4.76) id 1RK3ya-0007Hx-C6
	for bitcoin-development@lists.sourceforge.net;
	Sat, 29 Oct 2011 08:09:13 +0000
Received: by ggnj1 with SMTP id j1so5256196ggn.34
	for <bitcoin-development@lists.sourceforge.net>;
	Sat, 29 Oct 2011 01:09:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.2.164 with SMTP id 4mr1303879obv.49.1319875746833; Sat, 29
	Oct 2011 01:09:06 -0700 (PDT)
Received: by 10.182.55.227 with HTTP; Sat, 29 Oct 2011 01:09:06 -0700 (PDT)
In-Reply-To: <201110281956.04246.luke@dashjr.org>
References: <CABsx9T3Csb5qKTeEWoA_1_e0s0OnXFjxVpw2EV0RP+6hATeDrA@mail.gmail.com>
	<201110281956.04246.luke@dashjr.org>
Date: Sat, 29 Oct 2011 10:09:06 +0200
Message-ID: <CAJNQ0sv5tf5GAB=j9SYeC1ASzzKptJnoKt-tB7QD3dy_oG8L2Q@mail.gmail.com>
From: John Smith <witchspace81@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=f46d044519e109a3d604b06b8597
X-Spam-Score: -0.3 (/)
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
	(witchspace81[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
	digit (witchspace81[at]gmail.com)
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-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
	0.2 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RK3ya-0007Hx-C6
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] 0.5 release updated
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sat, 29 Oct 2011 08:09:13 -0000

--f46d044519e109a3d604b06b8597
Content-Type: text/plain; charset=ISO-8859-1

> Better would be a GUI=0/1 option to the bitcoin-qt.pro until a nicer
> (ideally
> automake/autoconf) system is implemented...
>

Are you sure you want to require qmake for the daemon build?

I agree having a unified build system would be nice, but qmake doesn't add
anything for non-qt software. Better to stick with a makefile.

If the goal is 'making it easier for the user' maybe it'd be best to make a
bash script that wraps both, that builds the daemon if possible, and the UI
if possible, and converts command line flags.

JS

--f46d044519e109a3d604b06b8597
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br>
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Better would be =
a GUI=3D0/1 option to the <a href=3D"http://bitcoin-qt.pro" target=3D"_blan=
k">bitcoin-qt.pro</a> until a nicer (ideally<br>

automake/autoconf) system is implemented...<br></blockquote><div><br>Are yo=
u sure you want to require qmake for the daemon build?<br><br>I agree havin=
g a unified build system would be nice, but qmake doesn&#39;t add anything =
for non-qt software. Better to stick with a makefile.<br>
<br>If the goal is &#39;making it easier for the user&#39; maybe it&#39;d b=
e best to make a bash script that wraps both, that builds the daemon if pos=
sible, and the UI if possible, and converts command line flags.<br><br>
JS<br></div></div>

--f46d044519e109a3d604b06b8597--