Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Qd3Oi-0007MI-9p for bitcoin-development@lists.sourceforge.net; Sat, 02 Jul 2011 16:50:24 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.160.175 as permitted sender) client-ip=209.85.160.175; envelope-from=witchspace81@gmail.com; helo=mail-gy0-f175.google.com; Received: from mail-gy0-f175.google.com ([209.85.160.175]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1Qd3Od-0000qq-T3 for bitcoin-development@lists.sourceforge.net; Sat, 02 Jul 2011 16:50:24 +0000 Received: by gyd12 with SMTP id 12so2135290gyd.34 for ; Sat, 02 Jul 2011 09:50:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.151.60.14 with SMTP id n14mr4228333ybk.72.1309625414449; Sat, 02 Jul 2011 09:50:14 -0700 (PDT) Received: by 10.151.150.15 with HTTP; Sat, 2 Jul 2011 09:50:14 -0700 (PDT) In-Reply-To: <201107021050.10563.luke@dashjr.org> References: <201107021050.10563.luke@dashjr.org> Date: Sat, 2 Jul 2011 16:50:14 +0000 Message-ID: From: John Smith To: Luke-Jr Content-Type: multipart/alternative; boundary=000325552e029dfbb504a718ed92 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: 1Qd3Od-0000qq-T3 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:50:24 -0000 --000325552e029dfbb504a718ed92 Content-Type: text/plain; charset=ISO-8859-1 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. JS --000325552e029dfbb504a718ed92 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Sat, Jul 2, 2011 at 2:50 PM, Luke-Jr <luke@dashjr.org> 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 o= f
> cmake?

I don't really care much either way, but cmake doesn't follow= the standard
build procedure (./configure && make && make install), thou= gh 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 .' i= s the most easy case :-) Probably it'd also need to pass through some c= ommand line args, for example --prefix.

JS

--000325552e029dfbb504a718ed92--