public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: John Smith <witchspace81@gmail.com>
To: Douglas Huff <dhuff@jrbobdobbs.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Reconsider build system change?
Date: Sat, 2 Jul 2011 18:03:49 +0000	[thread overview]
Message-ID: <CAJNQ0sv4i+wTQeGBmmfMpUL-mUB2a6KX1NddF2K4Lecs4ofuAA@mail.gmail.com> (raw)
In-Reply-To: <65026C81-A96E-490A-90D2-794A10C2A680@jrbobdobbs.org>

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

On Sat, Jul 2, 2011 at 5:45 PM, Douglas Huff <dhuff@jrbobdobbs.org> wrote:

> On Jul 2, 2011, at 12:31 PM, John Smith wrote:
> > So, what about native build script generation for other platforms?
> autotools can only generate makefiles (with at least two intermediate code
> generation steps), which is quite limited.
>
> This would be true if gmake didn't build/run basically everywhere; but, it
> does.
>

It doesn't for the native build systems on at least Windows and OSX. Yes,
you can get gmake to run, but it's a hack.


> I would say that's actually a mark against cmake. If you need a gui to
> select build options because your cli doesn't have proper help output
> something is wrong.
>

You don't need to use the UI. It's just a convenience. Command line can
simply be used if you want.


> If you're willing to setup and maintain a cmake build environment I
> wouldn't say it should be rejected outright. Speculating about it without an
> implementation to compare seems like a waste of time.
>

As I said in my opening post, there *is* a cmake build system implemented
for bitcoin.

JS

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

  reply	other threads:[~2011-07-02 18:03 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 [this message]
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=CAJNQ0sv4i+wTQeGBmmfMpUL-mUB2a6KX1NddF2K4Lecs4ofuAA@mail.gmail.com \
    --to=witchspace81@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=dhuff@jrbobdobbs.org \
    /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