1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <witchspace81@gmail.com>) id 1QcvL1-0003cn-4q
for bitcoin-development@lists.sourceforge.net;
Sat, 02 Jul 2011 08:14:03 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.175 as permitted sender)
client-ip=209.85.213.175; envelope-from=witchspace81@gmail.com;
helo=mail-yx0-f175.google.com;
Received: from mail-yx0-f175.google.com ([209.85.213.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QcvKw-0000Ca-O1
for bitcoin-development@lists.sourceforge.net;
Sat, 02 Jul 2011 08:14:03 +0000
Received: by yxi19 with SMTP id 19so312498yxi.34
for <bitcoin-development@lists.sourceforge.net>;
Sat, 02 Jul 2011 01:13:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.8.21 with SMTP id l21mr130680ybi.186.1309594432297; Sat,
02 Jul 2011 01:13:52 -0700 (PDT)
Received: by 10.151.150.15 with HTTP; Sat, 2 Jul 2011 01:13:52 -0700 (PDT)
In-Reply-To: <CAJNQ0stvozeQAVFkduY7Ph5EXy8ayYwiu4T+6Oz1RwjgiDnBeA@mail.gmail.com>
References: <CAJNQ0stvozeQAVFkduY7Ph5EXy8ayYwiu4T+6Oz1RwjgiDnBeA@mail.gmail.com>
Date: Sat, 2 Jul 2011 08:13:52 +0000
Message-ID: <CAJNQ0ssbonoe9cukoeyfTHykPPQZH+u=-v=29qMfCp-BKJB9+g@mail.gmail.com>
From: John Smith <witchspace81@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=000e0cd514ccefdbfe04a711b6ef
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(witchspace81[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (witchspace81[at]gmail.com)
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1QcvKw-0000Ca-O1
Subject: Re: [Bitcoin-development] Reconsider build system change?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sat, 02 Jul 2011 08:14:03 -0000
--000e0cd514ccefdbfe04a711b6ef
Content-Type: text/plain; charset=ISO-8859-1
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
>
--000e0cd514ccefdbfe04a711b6ef
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<br>Also important: it supports cross compiling:<br><br><a href=3D"http://w=
ww.cmake.org/Wiki/CMake_Cross_Compiling">http://www.cmake.org/Wiki/CMake_Cr=
oss_Compiling</a><br><br>JS<br><br><div class=3D"gmail_quote">On Sat, Jul 2=
, 2011 at 7:29 AM, John Smith <span dir=3D"ltr"><<a href=3D"mailto:witch=
space81@gmail.com">witchspace81@gmail.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Hello,<br><br>Why again did we choose for a=
utotools as future build system instead of cmake?<br><br>- CMake generates =
native build scripts for Make (all platforms), XCode, Visual Studio. Autoco=
nf only does Make.<br>
<br>- CMake has a clearer syntax, m4/autotools is very convoluted<br>
<br>- CMake is very fast<br><br>- CMake is supported natively in Qt Creator=
in the QT SDK, and is used by many other KDE/QT as well as other open sour=
ce applications. Many people discourage the use of autotools for new projec=
ts.<br>
<br>A CMake build system for bitcoin is already integrated into rpcminer, a=
vailable here:<br><br><a href=3D"http://luke.dashjr.org/programs/bitcoin/w/=
puddinpop-bitcoin-pool.git/tree" target=3D"_blank">http://luke.dashjr.org/p=
rograms/bitcoin/w/puddinpop-bitcoin-pool.git/tree</a><br>
<font color=3D"#888888">
<br>JS<br>
</font></blockquote></div><br>
--000e0cd514ccefdbfe04a711b6ef--
|
