Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Qd3UO-0001UM-KU for bitcoin-development@lists.sourceforge.net; Sat, 02 Jul 2011 16:56:16 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1Qd3UN-0001XR-Kl for bitcoin-development@lists.sourceforge.net; Sat, 02 Jul 2011 16:56:16 +0000 Received: from ishibashi.localnet (fl-67-77-87-72.dhcp.embarqhsd.net [67.77.87.72]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id F405C5605C1; Sat, 2 Jul 2011 16:56:07 +0000 (UTC) From: "Luke-Jr" To: John Smith Date: Sat, 2 Jul 2011 12:55:52 -0400 User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo; KDE/4.6.2; x86_64; ; ) References: <201107021050.10563.luke@dashjr.org> In-Reply-To: X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583 X-PGP-Key-ID: 665FC11DD53E9583 X-PGP-Keyserver: x-hkp://subkeys.pgp.net MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201107021255.54088.luke@dashjr.org> X-Spam-Score: -0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1Qd3UN-0001XR-Kl Cc: bitcoin-development@lists.sourceforge.net 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2011 16:56:16 -0000 On Saturday, July 02, 2011 12:50:14 PM John Smith wrote: > On Sat, Jul 2, 2011 at 2:50 PM, Luke-Jr 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. And --datadir --mandir --randomobscurecrap CXXFLAGS=-O9, etc Don't forget --help listing all the useful options... that's the big thing I miss with CMake-stuff.