On Fri, Jan 8, 2010 at 9:58 AM, Robert Bradshaw <rober...@math.washington.edu> wrote: > On Jan 8, 2010, at 7:02 AM, Dag Sverre Seljebotn wrote: > >> On Fri, 2010-01-08 at 06:51 -0800, dimpase wrote: >>> >>> On Jan 8, 9:59 pm, kcrisman <kcris...@gmail.com> wrote: >>>>> >>>>> no, it doesn't give you *any* reasonable figures, at all! >>>>> In fact, I am sure lots of people (a vast majority) are running Cygwin >>>>> (or Mingw - a clone of Cygwin) apps on their Windows boxes without >>>>> even realising this. Cygwin works quietly behind the scenes here. >>>> >>>> That is very interesting. When you say "a vast majority", can you >>>> give an example of a specific application people are using? That >>>> could be good to know about. >>> >>> a good and relevant to Sage example is GAP (which is also available >>> from within Sage) >>> A binary distribution of GAP for Windows consists (apart from the >>> common to all platforms code in GAP language etc) of an executable >>> built in Cygwin environment and linked against the Cygwin DLL, and the >>> latter DLL itself (and a DOS batch file to start the thing up). >>> That's all you need to run GAP on Windows, no fullblown Cygwin >>> environment is needed. >>> (you can try it yourself: www.gap-system.org) >>>> >>>> Also, from earlier in the discussion it sounded like it was possible >>>> to make Sage-Cygwin be a one-step download, e.g. >>>> >>>> 1. Download sage-cygwin.msi >>>> 2. Double click and click through an install process >>>> 3. Click the icon for sage-cygwin and begin using Sage >>>> >>>> If that is possible, that would be fantastic. Up to now my >>>> understanding was that one first had to download Cygwin and install/ >>>> configure it, then download the Sage install and hope that it >>>> cooperated with Cygwin on one's computer. >>> >>> no, I don't see any reason for this being impossible (see above). GAP >>> is basically like this, although it's packaged using zip... >> >> Well Sage is a bit different than this because you'd want the full set >> of tools for easy porting of SPKGs -- bash, tar, make, gcc, ... >> >> But they are just a few extra .exe files, really. There's likely no >> reason they couldn't be bundled with a Sage one-click installer and >> installed inside the sage /local/bin directory. There's no reason the >> user would need to ever see those tools unless one were debugging SPKG >> build failures etc. -- "!cmd" could always be manually redirected to >> Windows cmd.exe. >> >> For the more ambitious one could move away from SPKGs and find a fancier >> package solution with Windows compatability, leaving the DLL as the only >> trace of Cygwin (I don't really see the point though -- Cygwin is pretty >> small compared to a lot of the other stuff bundled with Sage!) > > For the record, this was already tried (using a combination of .bat files > and standalone javascript). The problem is that even fewer people > understood/were familiar with this build system than the dead-simple spkg > one, and it was Windows-only and had to be maintained completely separately. > Given the amount of other stuff that needs to be bundled, we might as well > get the whole thing. (Could it be completely separate from an existing > Cygwin, or is there only room for one Cygwin on a computer?) Also, as > mentioned %cython in the notebook couldn't work without gcc. >
An arbitrary number of Cygwin's can happily coexist. This is a brand new feature of the newest version of Cygwin. William
-- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
