On 2014-08-25, Julien Puydt <julien.pu...@laposte.net> wrote: > Hi, > > Le 25/08/2014 11:04, Dima Pasechnik a écrit : >> On 2014-08-25, Dr. David Kirkby (Kirkby Microwave Ltd) >> <drkir...@kirkbymicrowave.co.uk> wrote: >>> --089e01537eba8a9d2805016fca81 >>> Content-Type: text/plain; charset=UTF-8 >>> >>> It seems Sage really could do with a native windows port. I am wondering >>> how practical it would be to make a version which is a subset of Sage, with >>> something like Qt which runs on Windows, Linux, OSX and Solaris and has >>> the look and feel of those platforms. >> >> Sage components such as GAP, Singular, PARI/GP do not have native Windows >> ports. >> Without them you'd better run IPython directly, it will provide you better >> experience and roughly the same functionality. > > I don't understand why people insist on trying to build the windows port > on windows with cygwin ; it's also possible to cross-build windows ports : > http://wiki.ekiga.org/index.php/Building_Ekiga_for_Windows > > Of course, that requires some sanitization of build systems, clean > sources, etc...
Ekiga only does mingw(64/32) builds, but mingw does not provide enough POSIX (no fork(), etc). So the sources need to be worked on quite a bit... (and native mingw builds aren't so problematic, in fact) -- 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.
