public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
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 07:29:04 +0000	[thread overview]
Message-ID: <CAJNQ0stvozeQAVFkduY7Ph5EXy8ayYwiu4T+6Oz1RwjgiDnBeA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 649 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 796 bytes --]

             reply	other threads:[~2011-07-02  7:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-02  7:29 John Smith [this message]
2011-07-02  8:13 ` [Bitcoin-development] Reconsider build system change? 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
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=CAJNQ0stvozeQAVFkduY7Ph5EXy8ayYwiu4T+6Oz1RwjgiDnBeA@mail.gmail.com \
    --to=witchspace81@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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