From: John Smith <witchspace81@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Reconsider build system change?
Date: Sat, 2 Jul 2011 17:31:54 +0000 [thread overview]
Message-ID: <CAJNQ0stDg7qCxb8f-KjfP7k0RyM0dpHETkf==uswOzm4DstSUQ@mail.gmail.com> (raw)
In-Reply-To: <CAJNQ0su0jtaFz6abS+H24d7dqKoWkugct1yQLeVyXTgr0rkXXA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]
On Sat, Jul 2, 2011 at 5:05 PM, Douglas Huff <dhuff@jrbobdobbs•org> wrote:
> Cmake is just as bad as autotools, just with a different syntax and more
> "buzz" behind it right this second. I don't see any advantage to it over
> autotools unless you're not familiar with either and even then I wouldn't
> really call it an advantage. It's just different.
>
So, what about native build script generation for other platforms? autotools
can only generate makefiles (with at least two intermediate code generation
steps), which is quite limited.
IMO cmake is simple and elegant compared to the autotools monster. I don't
see why it would be "just as bad". And I have quite some experience with
both systems. Autotools is a hell to debug. cmake certainly isn't perfect,
but at least it's a leap forward.
It also requires a dependency that isn't installed by default anywhere, as
> already mentioned, and is less known outside of some obscure qt/kde circles
> and so finding people who are familiar with it and are willing to maintain
> it is more difficult.
>
Yes, apart from that only obscure projects such as LLVM, Blender, and
OpenCV are using it. Nothing of any importance.
BTW for cmake there is "ccmake" which is even better than configure --help
as it offers an interactive interface for configuration.
JS
[-- Attachment #2: Type: text/html, Size: 1908 bytes --]
next prev parent reply other threads:[~2011-07-02 17:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-02 7:29 John Smith
2011-07-02 8:13 ` John Smith
2011-07-02 11:30 ` Matt Corallo
2011-07-02 11:49 ` John Smith
2011-07-02 14:50 ` Luke-Jr
2011-07-02 16:50 ` John Smith
2011-07-02 16:55 ` Luke-Jr
2011-07-02 17:05 ` Douglas Huff
[not found] ` <CAJNQ0su0jtaFz6abS+H24d7dqKoWkugct1yQLeVyXTgr0rkXXA@mail.gmail.com>
2011-07-02 17:31 ` John Smith [this message]
2011-07-02 17:45 ` Douglas Huff
2011-07-02 18:03 ` John Smith
2011-07-02 18:12 ` Luke-Jr
2011-07-03 10:44 ` Pieter Wuille
2011-07-07 8:49 ` Pieter Wuille
2011-07-07 16:51 ` Jeff Garzik
2011-07-07 17:40 ` John Smith
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='CAJNQ0stDg7qCxb8f-KjfP7k0RyM0dpHETkf==uswOzm4DstSUQ@mail.gmail.com' \
--to=witchspace81@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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