On Thu, Jan 14, 2016 at 3:09 PM, Jean-Michaël Celerier <jeanmichael.celer...@gmail.com> wrote: > The problem is doing : > > list(LENGTH MyList NumList) > math(EXPR MaxItList ${NumList}-1) > > foreach(i RANGE ${MaxItList}) > list(GET MyOtherListOfSameSizeThanMyList ${i} Element) > foobazify(${Element}) > endforeach() > Probably a bad exmple, since you're not using MyList or i that simplifies to....
foreach( Element ${MyOtherListOfSameSizeThanMylist} ) foobazify( ${Element} ) endforeach() > instead of : > > for i in range(0, MyList.size): > foobazifiy(MyOtherListOfSameSizeThanMyList[i]) > > > > > > On Thu, Jan 14, 2016 at 2:08 PM, Charles Huet <charles.h...@gmail.com> > wrote: >> >> As long as CMake embeds everything that is required, I don't see the >> additional pain (since this is what it already does with the CMake >> language). >> >> >> Le jeu. 14 janv. 2016 à 13:35, Jean-Michaël Celerier >> <jeanmichael.celer...@gmail.com> a écrit : >>> >>> >>> On Wed, Jan 13, 2016 at 10:21 PM, Alexander Neundorf <neund...@kde.org> >>> wrote: >>>> >>>> >>>> My personal opinion: if the full power of python would be available, the >>>> build >>>> scripts would quickly turn into real programs, because programmers would >>>> be >>>> tempted to do so if all of python would be available. Then developers >>>> would >>>> have to understand two programs: the program itself, and the "build >>>> program". >>> >>> >>> The problem is when you have to do a real program for your build system >>> anyways (which occurs one day or another for any large enough project I >>> guess). >>> Currently it's a real pain (but it'd be even more painful to have to ship >>> Python / Bash / $script_language as part of your build system). >>> -- >>> >>> Powered by www.kitware.com >>> >>> Please keep messages on-topic and check the CMake FAQ at: >>> http://www.cmake.org/Wiki/CMake_FAQ >>> >>> Kitware offers various services to support the CMake community. For more >>> information on each offering, please visit: >>> >>> CMake Support: http://cmake.org/cmake/help/support.html >>> CMake Consulting: http://cmake.org/cmake/help/consulting.html >>> CMake Training Courses: http://cmake.org/cmake/help/training.html >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/cmake-developers > > > > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/cmake-developers -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers