On Saturday, 2 May 2015 08:25:15 UTC+1, Isuru Fernando wrote: > > Hi, > > What is the consensus on getting CMake into Sage? > > I made a ticket to get CMake into the optional packages list. > http://trac.sagemath.org/ticket/18078 > <http://trac.sagemath.org/ticket/18078>, so that CMake can be built from > source in Sage and the user does not have to make a system wide > installation. > > I'll work on getting CSymPy(github.com/sympy/csympy) into Sage this > summer. CSymPy uses CMake and I'd like a heads up on how to proceed. (If > CMake won't get into standard packages list in the future, then we'll have > to move to another build system as me and Ondřej would like to get CSymPy > into standard packages list) >
before cmake builds from source within Sage on OSX, using Sage's C/C++ toolchain, this is most probably not possible. And this seems to be hard to fix - it probably is a good illustration of cmake issues :-) > > Isuru > > > On Monday, February 9, 2015 at 6:07:40 PM UTC+5:30, Oleksandr Motsak wrote: >> >> AFAIR we had a preliminary cmake build system for legacy Singular but it >> is not yet ported to the current Singular (SW), >> whose build system is currently based on autoconf & automake. >> >> we may do that at some point. >> >> ps: IMHO following >> http://stackoverflow.com/questions/5971921/building-a-library-using-autotools-from-cmake >> >> would make it possible to approach that porting incrementally... >> >> Regards, >> >> -- >> Oleksandr >> >> >> On Sunday, February 8, 2015 at 2:18:30 PM UTC+1, Jakob Kroeker wrote: >>> >>> >Anyway, as mentioned before, according to this thread: >>> >>> > >>> http://groups.google.com/group/sage-devel/browse_thread/thread/e91a204a2902afd/ccbdaa4792872282?lnk=gst&q=Heads+up#ccbdaa4792872282 >>> >singular is migrating to CMake. >>> >>> For good or bad, Singular did not migrate to CMake. There was too much >>> opposition, I guess. >>> >> >> Am Montag, 1. März 2010 13:39:59 UTC+1 schrieb William: >>>> >>>> On Sun, Feb 28, 2010 at 11:40 PM, Peter Jeremy <peter...@acm.org> >>>> wrote: >>>> >>>> >>For what is worth, we use cmake in FEMhub (femhub.org) as a standard >>>> >>package and we never had any problems with that. >>>> > >>>> > If CMake was widely used (and hence can be listed as a prerequisite >>>> for >>>> > building Sage - like gmake, bash etc) then it would have no overhead >>>> > for Sage. >>>> >>>> CMake is definitely not as widely used as gmake and bash, so I'm >>>> against making it a prerequisite for Sage. In the history of the Sage >>>> project, the only prerequisite that was ever added was gfortran, and >>>> that is really part of GCC (Gnu Compiler Collection), so fairly >>>> standard. >>>> >>>> Anyway, as mentioned before, according to this thread: >>>> >>>> >>>> http://groups.google.com/group/sage-devel/browse_thread/thread/e91a204a2902afd/ccbdaa4792872282?lnk=gst&q=Heads+up#ccbdaa4792872282 >>>> >>>> singular is migrating to CMake. If that really happens, Sage will >>>> have to include CMake, whether we want to or not. >>>> >>>> -- William >>>> >>>> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
