summaryrefslogtreecommitdiff
path: root/04/130f41cac36a006d0150d8a84d6159048a49aa
blob: b5439bf94884f93efaf4ed4e36fa0eb9e5d49f78 (plain)
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
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <bitcoin-list@bluematt.me>) id 1QcyPD-0004SS-FD
	for bitcoin-development@lists.sourceforge.net;
	Sat, 02 Jul 2011 11:30:35 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bluematt.me
	designates 208.79.240.5 as permitted sender)
	client-ip=208.79.240.5; envelope-from=bitcoin-list@bluematt.me;
	helo=smtpauth.rollernet.us; 
Received: from smtpauth.rollernet.us ([208.79.240.5])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1QcyP8-0000gE-Mh
	for bitcoin-development@lists.sourceforge.net;
	Sat, 02 Jul 2011 11:30:35 +0000
Received: from smtpauth.rollernet.us (localhost [127.0.0.1])
	by smtpauth.rollernet.us (Postfix) with ESMTP id 7496C594008
	for <bitcoin-development@lists.sourceforge.net>;
	Sat,  2 Jul 2011 04:30:09 -0700 (PDT)
Received: from mail.bluematt.me (unknown
	[IPv6:2001:470:9ff2:2:20c:29ff:fe16:f239])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	(Authenticated sender: @bluematt.me)
	by smtpauth.rollernet.us (Postfix) with ESMTPSA
	for <bitcoin-development@lists.sourceforge.net>;
	Sat,  2 Jul 2011 04:30:07 -0700 (PDT)
Received: from [IPv6:2001:470:9ff2:1:2c0:caff:fe33:858b] (unknown
	[IPv6:2001:470:9ff2:1:2c0:caff:fe33:858b])
	by mail.bluematt.me (Postfix) with ESMTPSA id 889114EE5
	for <bitcoin-development@lists.sourceforge.net>;
	Sat,  2 Jul 2011 13:30:15 +0200 (CEST)
From: Matt Corallo <bitcoin-list@bluematt.me>
To: bitcoin-development@lists.sourceforge.net
In-Reply-To: <CAJNQ0ssbonoe9cukoeyfTHykPPQZH+u=-v=29qMfCp-BKJB9+g@mail.gmail.com>
References: <CAJNQ0stvozeQAVFkduY7Ph5EXy8ayYwiu4T+6Oz1RwjgiDnBeA@mail.gmail.com>
	<CAJNQ0ssbonoe9cukoeyfTHykPPQZH+u=-v=29qMfCp-BKJB9+g@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1";
	protocol="application/pgp-signature";
	boundary="=-kYBcJr+lxcYaWJb7SCj5"
Date: Sat, 02 Jul 2011 13:30:14 +0200
Message-ID: <1309606214.2285.54.camel@Desktop666>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2 
X-Rollernet-Abuse: Processed by Roller Network Mail Services. Contact
	abuse@rollernet.us to report violations. Abuse policy:
	http://rollernet.us/abuse.php
X-Rollernet-Submit: Submit ID 17d3.4e0f013f.43694.0
X-Spam-Score: -1.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 SPF_HELO_PASS          SPF: HELO matches SPF record
	-0.0 SPF_PASS               SPF: sender matches SPF record
X-Headers-End: 1QcyP8-0000gE-Mh
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 11:30:35 -0000


--=-kYBcJr+lxcYaWJb7SCj5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I dont think anyone really made a conscious decision one way or the
other, someone submitted an autotools patch and thus people started
talking about when we were going to merge autotools.  That said, the
autotools stuff needs redone before it would be merged anyway. So it
would be up to whoever writes the build system. However, autotools is
more standard than CMake, and since its a shell script, you dont have to
install CMake which doesnt come standard on almost any distros (AFAIK).

Matt

On Sat, 2011-07-02 at 08:13 +0000, John Smith wrote:
>=20
> Also important: it supports cross compiling:
>=20
> http://www.cmake.org/Wiki/CMake_Cross_Compiling
>=20
> JS
>=20
> On Sat, Jul 2, 2011 at 7:29 AM, John Smith <witchspace81@gmail.com>
> wrote:
>         Hello,
>        =20
>         Why again did we choose for autotools as future build system
>         instead of cmake?
>        =20
>         - CMake generates native build scripts for Make (all
>         platforms), XCode, Visual Studio. Autoconf only does Make.
>        =20
>         - CMake has a clearer syntax, m4/autotools is very convoluted
>        =20
>         - CMake is very fast
>        =20
>         - 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.
>        =20
>         A CMake build system for bitcoin is already integrated into
>         rpcminer, available here:
>        =20
>         http://luke.dashjr.org/programs/bitcoin/w/puddinpop-bitcoin-pool.=
git/tree
>        =20
>         JS
>=20
> -------------------------------------------------------------------------=
-----
> All of the data generated in your IT infrastructure is seriously valuable=
.
> Why? It contains a definitive record of application performance, security=
=20
> threats, fraudulent activity, and more. Splunk takes this data and makes=
=20
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________ Bitcoin-development maili=
ng list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge=
.net/lists/listinfo/bitcoin-development


--=-kYBcJr+lxcYaWJb7SCj5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAABAgAGBQJODwE4AAoJEBrh01BD4I5UJ0kP/RVvCz7uguQ1+Y8MSX2pVSHW
7o4A6TsOwvqfqgTadDM3VYNrc37u/vhcQD61GPfu8EVOmKLkltNrOAPJia0qzJ1u
67drPbI1dSRTLgX+vfQAKZbHXlACBjrah2g5pUGhllfT+LxB3aLH+0dYUZV46qYy
1MR+nyH8tygozLBEojqrItq3mJuTtbecYTO+r2GNwBiRCEmU9qAymzPfjAz8rX4i
LZkeBGi125FjVGBna9YuD+lC0AtbhHKmf+99OZ7CeQ+H9nTf0zHIQa1N5o0vDqWG
AYS6FxzTUsMsXxvaRYfY8qk4BLKsicSaf1bHlUVy6R57nMY9qgNJkwMdVW2qECJR
DpDwDJwGfp/k8IWSU+KfycDUreZ0HDJru1xay8hm7IMF41pI8bEZHEQvigA1zV3h
p/T+4iE8G8oAN9Z9OAY7pHWC/R+CS/BAkTfZqhd8mH1lt/4dBJ6ZN0LhfWihYs/d
hOqyvjmaxuITrnIbZ7tyVjwLF7T1spHCglosFTd4GWo2RYyIpYi4Q9q/nBEfT0Nj
ar6N9LUM6DenBJuOYAaaliFzlCMmUYF39hEo9pdPGeqR3gPrV7PoNdPBvMr2Bp4j
Me7XMEvEnloyXX28kk3LwRS2/1U0XPIZ9LeDn+2xSGq1DEh5JpOTksHLcUhtuKYM
pVGyTURxzGTdZPf57Sbp
=UsNX
-----END PGP SIGNATURE-----

--=-kYBcJr+lxcYaWJb7SCj5--