From: Matt Corallo <bitcoin-list@bluematt•me>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Reconsider build system change?
Date: Sat, 02 Jul 2011 13:30:14 +0200 [thread overview]
Message-ID: <1309606214.2285.54.camel@Desktop666> (raw)
In-Reply-To: <CAJNQ0ssbonoe9cukoeyfTHykPPQZH+u=-v=29qMfCp-BKJB9+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2257 bytes --]
I dont think anyone really made a conscious decision one way or the
other, someone submitted an autotools patch and thus people started
talking about when we were going to merge autotools. That said, the
autotools stuff needs redone before it would be merged anyway. So it
would be up to whoever writes the build system. However, autotools is
more standard than CMake, and since its a shell script, you dont have to
install CMake which doesnt come standard on almost any distros (AFAIK).
Matt
On Sat, 2011-07-02 at 08:13 +0000, John Smith wrote:
>
> Also important: it supports cross compiling:
>
> http://www.cmake.org/Wiki/CMake_Cross_Compiling
>
> JS
>
> On Sat, Jul 2, 2011 at 7:29 AM, John Smith <witchspace81@gmail•com>
> wrote:
> Hello,
>
> Why again did we choose for autotools as future build system
> instead of cmake?
>
> - CMake generates native build scripts for Make (all
> platforms), XCode, Visual Studio. Autoconf only does Make.
>
> - CMake has a clearer syntax, m4/autotools is very convoluted
>
> - CMake is very fast
>
> - CMake is supported natively in Qt Creator in the QT SDK, and
> is used by many other KDE/QT as well as other open source
> applications. Many people discourage the use of autotools for
> new projects.
>
> A CMake build system for bitcoin is already integrated into
> rpcminer, available here:
>
> http://luke.dashjr.org/programs/bitcoin/w/puddinpop-bitcoin-pool.git/tree
>
> JS
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists•sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-07-02 11:30 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 [this message]
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
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=1309606214.2285.54.camel@Desktop666 \
--to=bitcoin-list@bluematt$(echo .)me \
--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