From: Thomas Guyot-Sionnest <dermoth@aei•ca>
To: Kosta Zertsekel <zertsekel@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Jeffrey Paul <jp@eeqj•com>
Subject: Re: [bitcoin-dev] Bitcoin Core build system (automake vs cmake)
Date: Tue, 24 Oct 2017 11:25:19 -0400 [thread overview]
Message-ID: <20470035-2199-d822-f97a-11611a71f490@aei.ca> (raw)
In-Reply-To: <CADxo8WLk_Ttaa3-jXQXaCJ3E+tKH9J7uUFAN_pfvtWOx_77cAA@mail.gmail.com>
On 23/10/17 07:52 AM, Kosta Zertsekel via bitcoin-dev wrote:
> >> 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
> <mailto: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...
>
> [...]
>
> 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?
What exact problem are you trying to fix for bitcoin-core?
Each build system have their pros and cons, and what you need it the
right tool for the job. Unless there is a specific problem to solve and
that cmake can solve it without causing other issues, why would you want
to change?
Or better yet, convert yourself bitcoin-core to cmake and show the
developers that it makes build config simpler without scarifying
features (cross-platform builds, gitian...) then maybe they'll adopt it.
Regards,
--
Thomas
prev parent reply other threads:[~2017-10-24 15:25 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
2017-10-24 15:25 ` Thomas Guyot-Sionnest [this message]
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=20470035-2199-d822-f97a-11611a71f490@aei.ca \
--to=dermoth@aei$(echo .)ca \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jp@eeqj$(echo .)com \
--cc=zertsekel@gmail$(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