public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@exmulti.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Reconsider build system change?
Date: Thu, 7 Jul 2011 12:51:08 -0400	[thread overview]
Message-ID: <CA+8xBpcj5LGs2=v5BhwvOAAntxPCAo-KKBpJLs9Z_B3OAu+xDg@mail.gmail.com> (raw)
In-Reply-To: <20110707084937.GA10392@ulyssis.org>

On Thu, Jul 7, 2011 at 4:49 AM, Pieter Wuille <pieter.wuille@gmail.com> wrote:
> On Sun, Jul 03, 2011 at 12:44:17PM +0200, Pieter Wuille wrote:
>> I have no preference for any particular project build system. If a system
>> * is easy enough to set up (included in standard repositories, eg.)
>> * allows building of the bitcoin codebase on several linux distro's
>> * does cross-compilation to windows
>> * supports osx
>> * is easy to maintain
>> * it is not too hard to adapt other GUI's to use it (bitcoin-qt,
>>   maybe others as well, i hear about a cocoabitcoin?)
>> * gets implemented and tested to support all of the above
>> .. i have no problem with choosing that system for future versions.
>
> Other opinions? Someone actually interested in writing a cmake configuration
> for bitcoin?

autotools is indeed "the devil we know" which works automatically on
all supported platforms save VC++  It is also the easiest to package,
as all distros already have macros and scripts specifically designed
to integrate autotools packages into their package build systems.
cmake simply does not have that level of uptake.

-- 
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com



  reply	other threads:[~2011-07-07 16:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-02  7:29 [Bitcoin-development] Reconsider build system change? 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
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 [this message]
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='CA+8xBpcj5LGs2=v5BhwvOAAntxPCAo-KKBpJLs9Z_B3OAu+xDg@mail.gmail.com' \
    --to=jgarzik@exmulti.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=pieter.wuille@gmail.com \
    /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