[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cmake
Subject:    Re: [CMake] improve the CMake language?
From:       "P. Fleury" <fleury () users ! sourceforge ! net>
Date:       2007-11-08 15:10:02
Message-ID: f473c7de0711080710t43a99dedtdd0f290b533323f2 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On 11/8/07, Bill Hoffman <bill.hoffman@kitware.com> wrote:
>
> Gonzalo Garramu=F1o wrote:




> [...] Also, I am
> not sure having N languages for CMake would be the best approach.  So,
> you go to build a project, and hey they are using CMake, cool, I know
> how to run CMake, oh wait, that one is ruby CMake, I need to get the
> ruby CMake to build it.  Would Kitware have to distribute N binaries?
> One of the biggest complaints about CMake, is that it requires CMake to
> be installed in order to do the build.  What if it required N different
> binaries where N was decided on by the project doing the build.  I just
> don't think that would be in the best interest of the community.  At the
> end of the day CMake should be like make, it should be a binary utility
> that is available by default on every OS.  It is a single interface so
> that if you know how to use it in one place you can use it in another.


I totally agree with this point. The least I want is to have to
configure/build the build system before I get to the actual project. That,
from my POV, also applies to the 'language as a plugin to cmake' approach,
as one may not have the appropriate plugin to build project X, and has to
download/built it from svn etc. I feel this is way more pain in the long ru=
n
than being stuck with a particular programming language.



-Bill
>
>
> -Bill
>
> _______________________________________________
> CMake mailing list
> CMake@cmake.org
> http://www.cmake.org/mailman/listinfo/cmake
>

[Attachment #5 (text/html)]

<br><div><span class="gmail_quote">On 11/8/07, <b class="gmail_sendername">Bill \
Hoffman</b> &lt;<a href="mailto:bill.hoffman@kitware.com">bill.hoffman@kitware.com</a>&gt; \
wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, \
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Gonzalo Garramuņo \
wrote:</blockquote><div><br>&nbsp;</div><blockquote class="gmail_quote" \
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; \
padding-left: 1ex;">[...] Also, I am<br>not sure having N languages for CMake would \
be the best approach.&nbsp;&nbsp;So, <br>you go to build a project, and hey they are \
using CMake, cool, I know<br>how to run CMake, oh wait, that one is ruby CMake, I \
need to get the<br>ruby CMake to build it.&nbsp;&nbsp;Would Kitware have to \
distribute N binaries?<br> One of the biggest complaints about CMake, is that it \
requires CMake to<br>be installed in order to do the build.&nbsp;&nbsp;What if it \
required N different<br>binaries where N was decided on by the project doing the \
build.&nbsp;&nbsp;I just <br>don&#39;t think that would be in the best interest of \
the community.&nbsp;&nbsp;At the<br>end of the day CMake should be like make, it \
should be a binary utility<br>that is available by default on every OS.&nbsp;&nbsp;It \
is a single interface so <br>that if you know how to use it in one place you can use \
it in another.</blockquote><div><br>I totally agree with this point. The least I want \
is to have to configure/build the build system before I get to the actual project. \
That, from my POV, also applies to the &#39;language as a plugin to cmake&#39; \
approach, as one may not have the appropriate plugin to build project X, and has to \
download/built it from svn etc. I feel this is way more pain in the long run than \
being stuck with a particular programming language. <br><br><br></div><br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: \
1ex;">-Bill<br><br><br>-Bill<br><br>_______________________________________________ \
<br>CMake mailing list<br><a href="mailto:CMake@cmake.org">CMake@cmake.org</a><br><a \
href="http://www.cmake.org/mailman/listinfo/cmake">http://www.cmake.org/mailman/listinfo/cmake</a><br></blockquote></div><br>




_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

[prev in list] [next in list] [prev in thread] [next in thread]