<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style='font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;'>Hi David,<br><br>This is a resend of an email I sent earlier.<br><br>RE:<br><div class="zmail_extra"><div id="1"><br>---- On Mon, 20 Jun 2016 19:05:23 -0400 <b>David T. Lewis <lewis@mail.msen.com></b> wrote ---- <br></div><blockquote style="border-left: 1px solid #0000FF;padding-left: 6px; margin: 0 0 0 5px"><div> <br>On Mon, Jun 20, 2016 at 10:06:28PM +0200, Holger Freyther wrote: <br>> <br>> <br>> > On 18 Jun 2016, at 23:28, <a href="mailto:commits@source.squeak.org" target="_blank">commits@source.squeak.org</a> wrote: <br>> > <br>> > <br>> > Timothy M uploaded a new version of CMakeVMMakerSqueak to project VM Maker: <br>> > <a href="http://source.squeak.org/VMMaker/CMakeVMMakerSqueak-tty.126.mcz" target="_blank">http://source.squeak.org/VMMaker/CMakeVMMakerSqueak-tty.126.mcz</a> <br>> <br>> Hi, <br>> <br>> I might be teared and feathered but what would it take to maintain the CMakeLists.txt directly in git and not of generate them from Smalltalk? <br>> <br> <br>That is exactly how Ian Piumarta's CMake build system has been working <br>for the last 6 years or so. It is done with a relatively small amount of <br>CMake scripting code, and has been working reliably with only minimal <br>maintenance since it was first put in place. <br> <br>My earlier comments on this topic are here (my references to the Subversion <br>repository would now pertain to the new Github repository): <br> <a href="http://lists.squeakfoundation.org/pipermail/vm-dev/2014-May/015313.html" target="_blank">http://lists.squeakfoundation.org/pipermail/vm-dev/2014-May/015313.html</a> <br> <br> <br>> From my limited point of view it seems cmake supports targeting multiple platforms/configurations from within the CMakeLists. And when trying to build the PharoVM on FreeBSD I had a lot of trouble[1] and waited[2] a bit too much. <br>> <br> <br>Yes, that is the purpose of CMake. It is designed to be a platform independent <br>build tool. If you find yourself creating large quantities of platform specific <br>CMake scripts, it is a sign that something is wrong. <br> <br>So it certainly does make sense for the CMakeLists to be maintained and <br>versioned along with the source code to which they apply. No need for any <br>tar and feathers IMHO :-) <br> <br>Dave <br> <br> <br> <br>> kind regards <br>> <br>> holger <br>> <br>> <br>> <br>> [1] Trouble in the sense that the generated paths were absolute, that some CFLAGS didn't apply to the compiler used. <br>> <br>> [2] I seem to have failed to just generate the CMakeLists.txt/* and decided to generate everything which took some time. E.g. the files not being truncated before they are written to <br></div></blockquote><br><br>There is a good chance that you and holger are correct. Also, the CMakeVMMakerSqueak itself will need crowd-sourcing to build out the various build types, so, since crowd-sourcing needs to be done, why not do it directly an example CMake build tree (I have 3 that can be generated) and use the git for developing them?<br><br>There is significant work remaining to get the CMakeVMMakerSqueak use documented, simplified (and some refactoring in plugins to be done). I would rather avoid that work (and move on to other projects) if the community can make better progress with straight CMake build scripts.<br><br>Let me know what your decision is. <br><br>cheers,<br><br>t<br><br><br><br><br><br><br><br><br><br><br></div><br></div></body></html>