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; 
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
Subject: Re: [Bitcoin-development] Reconsider build system change?
Precedence: list


--=-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--