public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: John Smith <witchspace81@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin-qt ready for merging
Date: Thu, 1 Sep 2011 02:32:52 +0000	[thread overview]
Message-ID: <CAJNQ0sve5iSrxXtAEc2-XZpD+3GtYNa9_yc0+yYd0_YZiHHK8A@mail.gmail.com> (raw)
In-Reply-To: <201108312213.38213.luke@dashjr.org>

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

On Thu, Sep 1, 2011 at 2:13 AM, Luke-Jr <luke@dashjr.org> wrote:

> On Wednesday, August 31, 2011 10:20:48 AM John Smith wrote:
> > The project builds on Windows, MacOSX and Linux using qmake.
>
> How do you set build options with qmake?
>

You can put assignments on the commandline; for example,

qmake "CONFIG+=test" test.pro

Like in plain make, these variables can be used for conditionally
enabling/disabling libraries or other options in the .pro file.

http://doc.qt.nokia.com/latest/qmake-manual.html

(reminds me that I still need to add the USE_UPNP option)

Note that qmake is a pretty simple tool, optimized for conveniently building
Qt applications in a cross-platform way; it in no way compares to
cmake/autotools or another "full" build system. But it's enough for building
bitcoin-qt on the supported target architectures so that's good enough for
me... For "bitcoind" and "bitcoin-wx" you probably want to keep around the
makefile.

JS

[-- Attachment #2: Type: text/html, Size: 1409 bytes --]

  reply	other threads:[~2011-09-01  2:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31 14:20 [Bitcoin-development] Bitcoin-qt ready for merging 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 [this message]
2011-09-22 20:11 ` Luke-Jr
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=CAJNQ0sve5iSrxXtAEc2-XZpD+3GtYNa9_yc0+yYd0_YZiHHK8A@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