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
|
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 <witchspace81@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>;
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: <CAJNQ0stvozeQAVFkduY7Ph5EXy8ayYwiu4T+6Oz1RwjgiDnBeA@mail.gmail.com>
<201107021050.10563.luke@dashjr.org>
Date: Sat, 2 Jul 2011 16:50:14 +0000
Message-ID: <CAJNQ0svyJcob=gfWfi7YuLWTdbLokrFyDGnMFtYLRk_29r-DZw@mail.gmail.com>
From: John Smith <witchspace81@gmail.com>
To: Luke-Jr <luke@dashjr.org>
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: <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 16:50:24 -0000
--000325552e029dfbb504a718ed92
Content-Type: text/plain; charset=ISO-8859-1
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 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 <span dir=3D"ltr"><<a href=3D"ma=
ilto:luke@dashjr.org">luke@dashjr.org</a>></span> wrote:<br><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">On Saturday, July 02, 2011 3:29:04 AM John Smith wrote:<b=
r>
> Why again did we choose for autotools as future build system instead o=
f<br>
> cmake?<br>
<br>
</div>I don't really care much either way, but cmake doesn't follow=
the standard<br>
build procedure (./configure && make && make install), thou=
gh I imagine<br>
./configure could be emulated with some script.<br>
</blockquote></div><br>It would change the sequence to<br>
<br>
cmake . && make && make install<br>
<br>
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.<br>
<br>
JS<br><br>
--000325552e029dfbb504a718ed92--
|
