From: Douglas Huff <dhuff@jrbobdobbs•org>
To: John Smith <witchspace81@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Reconsider build system change?
Date: Sat, 2 Jul 2011 12:05:51 -0500 [thread overview]
Message-ID: <1DBB0EED-7A9C-46AC-ABE2-6214ABD3FE9A@jrbobdobbs.org> (raw)
In-Reply-To: <CAJNQ0svyJcob=gfWfi7YuLWTdbLokrFyDGnMFtYLRk_29r-DZw@mail.gmail.com>
Cmake is just as bad as autotools, just with a different syntax and more "buzz" behind it right this second. I don't see any advantage to it over autotools unless you're not familiar with either and even then I wouldn't really call it an advantage. It's just different.
It also requires a dependency that isn't installed by default anywhere, as already mentioned, and is less known outside of some obscure qt/kde circles and so finding people who are familiar with it and are willing to maintain it is more difficult.
Autotools is the devil you know.
You'll probably throw out that mysql and compiz have switched to it, but really, those projects aren't something that should be emulated by anyone. Ever.
On Jul 2, 2011, at 11:50 AM, John Smith wrote:
> On Sat, Jul 2, 2011 at 2:50 PM, Luke-Jr <luke@dashjr•org> wrote:
> On Saturday, July 02, 2011 3:29:04 AM John Smith wrote:
> > Why again did we choose for autotools as future build system instead of
> > cmake?
>
> I don't really care much either way, but cmake doesn't follow the standard
> build procedure (./configure && make && make install), though I imagine
> ./configure could be emulated with some script.
>
> It would change the sequence to
>
> cmake . && make && make install
>
> So a shell script named 'configure' that starts 'cmake .' is the most easy case :-) Probably it'd also need to pass through some command line args, for example --prefix.
>
> 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
--
Douglas Huff
next prev parent reply other threads:[~2011-07-02 17:06 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
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 [this message]
[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=1DBB0EED-7A9C-46AC-ABE2-6214ABD3FE9A@jrbobdobbs.org \
--to=dhuff@jrbobdobbs$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=witchspace81@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