From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Qcudc-0002Uv-J6 for bitcoin-development@lists.sourceforge.net; Sat, 02 Jul 2011 07:29:12 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.161.175 as permitted sender) client-ip=209.85.161.175; envelope-from=witchspace81@gmail.com; helo=mail-gx0-f175.google.com; Received: from mail-gx0-f175.google.com ([209.85.161.175]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1Qcuda-0005or-4I for bitcoin-development@lists.sourceforge.net; Sat, 02 Jul 2011 07:29:12 +0000 Received: by gxk3 with SMTP id 3so2026764gxk.34 for ; Sat, 02 Jul 2011 00:29:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.151.29.18 with SMTP id g18mr3450807ybj.362.1309591744510; Sat, 02 Jul 2011 00:29:04 -0700 (PDT) Received: by 10.151.50.21 with HTTP; Sat, 2 Jul 2011 00:29:04 -0700 (PDT) Date: Sat, 2 Jul 2011 07:29:04 +0000 Message-ID: From: John Smith To: Bitcoin Dev Content-Type: multipart/alternative; boundary=000e0cd24af4bb79be04a7111690 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: 1Qcuda-0005or-4I Subject: [Bitcoin-development] Reconsider build system change? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2011 07:29:12 -0000 --000e0cd24af4bb79be04a7111690 Content-Type: text/plain; charset=ISO-8859-1 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 --000e0cd24af4bb79be04a7111690 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello,

Why again did we choose for autotools as future build system = instead of cmake?

- CMake generates native build scripts for Make (a= ll platforms), XCode, Visual Studio. Autoconf only does Make.

- CMak= e 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 sour= ce applications. Many people discourage the use of autotools for new projec= ts.

A CMake build system for bitcoin is already integrated into rpcminer, a= vailable here:

http://luke.dashjr.org/programs/bitcoin/w/= puddinpop-bitcoin-pool.git/tree

JS
--000e0cd24af4bb79be04a7111690--