<html><head><meta name="qrichtext" content="1" /></head><body style="font-size:10pt;font-family:DejaVu Sans">
<p>Am Sonntag 02 Juli 2006 07:25 schrieb Stephan Kulow:</p>
<p>> Am Sonntag, 2. Juli 2006 06:08 schrieb Michael Pyne:</p>
<p>> > It sounds useful to me if it does nothing more than transform</p>
<p>> > --prefix=foo and --disable-debug to the CMake equivalents. And I don't</p>
<p>> > see a reason to force people to have to read CMake documentation when</p>
<p>> > ./configure && make && make install works for 95% of the other software</p>
<p>> > out there.</p>
<p>></p>
<p>> Yeah, but for KDE it will be ./configure && cd build && make && make</p>
<p>> install</p>
<p>></p>
<p>> So we already have the first difference you have to read about. And if</p>
<p>> you're there, you can just as well go the full route. I'd vote against the</p>
<p>> introduction of this placebo script. I'd rather add a configure script that</p>
<p>> will output the cmake command to call. So if you</p>
<p>> go ./configure --prefix /usr, it will say "KDE does not use autoconf</p>
<p>> anymore, next time use cmake -D..." (and I do have to admit I don't know</p>
<p>> the exact D options, --prefix is easier :)</p>
<p></p>
<p>Yes, this sounds good.</p>
<p></p>
<p>Here's the intro:</p>
<p>http://wiki.kde.org/tiki-index.php?page=KDECMakeIntro#id140643</p>
<p></p>
<p>Bye</p>
<p>Alex</p>
<p></p>
</body></html>