📅 Original date posted:2011-08-31
🗒️ Summary of this message: Luke-Jr asks how to set build options with qmake. You can put assignments on the command line, and these variables can be used for conditionally enabling/disabling libraries or other options in the .pro file.
📝 Original message:On Thu, Sep 1, 2011 at 2:13 AM, Luke-Jr <luke at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110901/b7a21c59/attachment.html>;
John Smith [ARCHIVE] /
npub1e4…4jafl
2023-06-07 02:20:00
in reply to nevent1q…kft7
Author Public Key
npub1e4lupyw4vuuhfsmt726ud69555re66pph90kwx0afpt346e9k7zsd4jaflPublished at
2023-06-07 02:20:00Event JSON
{
"id": "b9538a95af7c3a9238c38c8c060380a363513b4e3a1fcd47101406d84cd43279",
"pubkey": "cd7fc091d5673974c36bf2b5c6e8b4a5079d6821b95f6719fd48571aeb25b785",
"created_at": 1686104400,
"kind": 1,
"tags": [
[
"e",
"ae205b1e3dc9858e8c5287dab16a9d15c248143003d13a23e95b51e3687a0e4a",
"",
"root"
],
[
"e",
"cd0a79dc4f6c004770587d4d1546813f35c62c227c3e4ca60e63b3748ad08140",
"",
"reply"
],
[
"p",
"6ac6a519b554d8ff726a301e3daec0b489f443793778feccc6ea7a536f7354f1"
]
],
"content": "📅 Original date posted:2011-08-31\n🗒️ Summary of this message: Luke-Jr asks how to set build options with qmake. You can put assignments on the command line, and these variables can be used for conditionally enabling/disabling libraries or other options in the .pro file.\n📝 Original message:On Thu, Sep 1, 2011 at 2:13 AM, Luke-Jr \u003cluke at dashjr.org\u003e wrote:\n\n\u003e On Wednesday, August 31, 2011 10:20:48 AM John Smith wrote:\n\u003e \u003e The project builds on Windows, MacOSX and Linux using qmake.\n\u003e\n\u003e How do you set build options with qmake?\n\u003e\n\nYou can put assignments on the commandline; for example,\n\nqmake \"CONFIG+=test\" test.pro\n\nLike in plain make, these variables can be used for conditionally\nenabling/disabling libraries or other options in the .pro file.\n\nhttp://doc.qt.nokia.com/latest/qmake-manual.html\n\n(reminds me that I still need to add the USE_UPNP option)\n\nNote that qmake is a pretty simple tool, optimized for conveniently building\nQt applications in a cross-platform way; it in no way compares to\ncmake/autotools or another \"full\" build system. But it's enough for building\nbitcoin-qt on the supported target architectures so that's good enough for\nme... For \"bitcoind\" and \"bitcoin-wx\" you probably want to keep around the\nmakefile.\n\nJS\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110901/b7a21c59/attachment.html\u003e",
"sig": "597dde4712e1e255a755cfaac7459eb090294f6d5fe2c16da610083223506ce21b84f4c32cd84024deabbd4207ddb123877b5814cf1d3fccc0f91d9c318f51e6"
}