Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Qyx5T-00012E-DE for bitcoin-development@lists.sourceforge.net; Thu, 01 Sep 2011 02:33:03 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.218.47 as permitted sender) client-ip=209.85.218.47; envelope-from=witchspace81@gmail.com; helo=mail-yi0-f47.google.com; Received: from mail-yi0-f47.google.com ([209.85.218.47]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Qyx5P-0002qW-1P for bitcoin-development@lists.sourceforge.net; Thu, 01 Sep 2011 02:33:03 +0000 Received: by yia28 with SMTP id 28so1375629yia.34 for ; Wed, 31 Aug 2011 19:32:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.170.8 with SMTP id s8mr1027409ybe.28.1314844372508; Wed, 31 Aug 2011 19:32:52 -0700 (PDT) Received: by 10.150.146.2 with HTTP; Wed, 31 Aug 2011 19:32:52 -0700 (PDT) In-Reply-To: <201108312213.38213.luke@dashjr.org> References: <201108312213.38213.luke@dashjr.org> Date: Thu, 1 Sep 2011 02:32:52 +0000 Message-ID: From: John Smith To: Luke-Jr Content-Type: multipart/alternative; boundary=000e0cd3aec0c21ed304abd80f6d X-Spam-Score: -0.1 (/) 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) 0.0 T_FRT_PROFILE1 BODY: ReplaceTags: Profile (1) 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.4 AWL AWL: From: address is in the auto white-list X-Headers-End: 1Qyx5P-0002qW-1P Cc: bitcoin-development@lists.sourceforge.net 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, 01 Sep 2011 02:33:03 -0000 --000e0cd3aec0c21ed304abd80f6d Content-Type: text/plain; charset=ISO-8859-1 On Thu, Sep 1, 2011 at 2:13 AM, Luke-Jr 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 --000e0cd3aec0c21ed304abd80f6d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

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 wrot= e:
> 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 exam= ple,

qmake "CONFIG+=3Dtest" te= st.pro

Like in plain make, these variables can be used for condi= tionally 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-platfo= rm way; it in no way compares to cmake/autotools or another "full"= ; build system. But it's enough for building bitcoin-qt on the supporte= d target architectures so that's good enough for me... For "bitcoi= nd" and "bitcoin-wx" you probably want to keep around the ma= kefile.

JS

--000e0cd3aec0c21ed304abd80f6d--