On Sun, Feb 28, 2010 at 7:34 AM, Bjarke Hammersholt Roune <bjarke.ro...@gmail.com> wrote: > Can a standard spkg in Sage use CMake? > > http://www.cmake.org/ > > I ask because I'm seriously considering moving from a straight make > system for Frobby to CMake, but if that is not possible for Sage then > it's a non-starter. A search of sage-devel reveals that Singular is > moving to CMake, but it isn't clear to me from the discussion how well > Sage is able to deal with CMake at this time. >
No, at present, it is definitely not OK for a standard spkg to use CMake. Frobby is an optional spkg, not standard, so I guess it would be OK, though if you use CMake, note that the vast majority of people that try to build Frobby will find that it immediately fails fro them, until they install cmake, which they may not easily be able to do. If Singular moves to CMake that could seriously be a pain for us, since we'll likely have to add cmake as a standard package to Sage, which will of course involves headaches. CMake is not nearly as widely deployed as many of the components of Sage that we do build from source, so assuming it is installed already is not so reasonable. So quick summary: Right now Sage does not include cmake, so no standard package can depend on cmake. If we are forced into including cmake because of a design decision by Singular that we can't get around, then we'll have to get cmake into sage as a standard package. At that point, any standard package could use cmake. By the way, the cmake source tarball is about 3.4MB and takes 4 minutes to compile on sage.math. So size and time wise it is not unreasonable that it could be a standard Sage package at some point. -- william -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
