From: Kosta Zertsekel <zertsekel@gmail•com>
To: Jeffrey Paul <jp@eeqj•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin Core build system (automake vs cmake)
Date: Mon, 23 Oct 2017 04:52:04 -0700 [thread overview]
Message-ID: <CADxo8WLk_Ttaa3-jXQXaCJ3E+tKH9J7uUFAN_pfvtWOx_77cAA@mail.gmail.com> (raw)
In-Reply-To: <FB8D6509-5C2E-4F4F-9D7F-6CFB90591FB0@eeqj.com>
[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]
>> On Oct 22, 2017, at 13:11, Kosta Zertsekel wrote:
>> I wonder why automake has become the build system for Bitcoin Core?
>> I mean - why not cmake which is considered better?
>> Can you please point to the relevant discussion or explanation?
> On Mon, Oct 23, 2017 at 6:24 AM, Jeffrey Paul <jp@eeqj•com> wrote:
> Considered by whom? Automake is the standard and I prefer it as it
requires
> no additional install on most systems. For that, I consider it better.
Well, here are some quotes about CMake build tools...
JetBrains (2014)
================
Our brief research showed that CMake and ‘make’ were the most popular
cross-platform tools, having ~30% of users each, while both Autotools
and qmake had less than 7% of users. So we ended up with CMake and make.
[https://blog.jetbrains.com/clion/2014/09/cmake-vs-the-others-round-1/]
KDE Project (2006)
==================
Now the next big change is happening: KDE is leaving the aging "autotool"
build chain behind. Some developers, not only in KDE, like to nickname
the autotools as "auto-hell" because of its difficult to comprehend
architecture. So, KDE 4 will feature a completely different build system:
CMake.
[https://lwn.net/Articles/188693/]
Also, there are more advanced build systems:
============================================
- Meson [http://mesonbuild.com]
- Ninja [https://ninja-build.org/]
All of them (CMake, Meson, Ninja) had a goal to replace automake.
Was there any discussion about choosing the best build system for
Bitcoin Core?
Thanks,
--- Kosta Z.
[-- Attachment #2: Type: text/html, Size: 5004 bytes --]
next prev parent reply other threads:[~2017-10-23 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-22 17:11 Kosta Zertsekel
[not found] ` <FB8D6509-5C2E-4F4F-9D7F-6CFB90591FB0@eeqj.com>
2017-10-23 11:52 ` Kosta Zertsekel [this message]
2017-10-24 15:25 ` Thomas Guyot-Sionnest
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=CADxo8WLk_Ttaa3-jXQXaCJ3E+tKH9J7uUFAN_pfvtWOx_77cAA@mail.gmail.com \
--to=zertsekel@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jp@eeqj$(echo .)com \
/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