From: John Smith <witchspace81@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] 0.5 release updated
Date: Sat, 29 Oct 2011 10:09:06 +0200 [thread overview]
Message-ID: <CAJNQ0sv5tf5GAB=j9SYeC1ASzzKptJnoKt-tB7QD3dy_oG8L2Q@mail.gmail.com> (raw)
In-Reply-To: <201110281956.04246.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 534 bytes --]
> 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
[-- Attachment #2: Type: text/html, Size: 798 bytes --]
prev parent reply other threads:[~2011-10-29 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 18:33 [Bitcoin-development] 0.5 release updated Gavin Andresen
2011-10-28 23:56 ` Luke-Jr
2011-10-29 8:09 ` John Smith [this message]
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='CAJNQ0sv5tf5GAB=j9SYeC1ASzzKptJnoKt-tB7QD3dy_oG8L2Q@mail.gmail.com' \
--to=witchspace81@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=luke@dashjr.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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