Differences between revisions 1 and 4 (spanning 3 versions)
Revision 1 as of 2008-04-16 23:47:00
Size: 604
Comment: copy of the "proposed timeline" section from the windows page
Revision 4 as of 2008-04-17 01:39:39
Size: 958
Comment: add link back to global "Sage on Windows" page
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== Available Toolchains on Windows ==
Line 7: Line 9:

== Goals ==

=== Until Dev1 in Seattle ===

 * document tool chain setup
 * get people caught up to speed with tool chain and/or Sage's internal structure [in case they need it]
 * get pari and its dependencies working with MSVC 64 bit
 * analyze what needs to be done to get R up and running with MSVC

Available Toolchains on Windows

Proposed

  • Get Cygwin port working again. This depends on libSingular working. The Singular team would be very happy if this happened
  • Take standalone applications and move them over to MinGW and/or MSVC if possible, i.e. the Salami tactic
  • port pexpect to native Windows API - this is needed for MinGW/MSVC to work
  • Once pexpect works we should combine the notebook, matplotlib-based plotting code, the calculus code and maxima to have a basic program useful to a lot of people
  • port the remaining C/C++/Fortran code over to the new toolchain and get closer to a full working Sage

Goals

Until Dev1 in Seattle

  • document tool chain setup
  • get people caught up to speed with tool chain and/or Sage's internal structure [in case they need it]
  • get pari and its dependencies working with MSVC 64 bit
  • analyze what needs to be done to get R up and running with MSVC