[petsc-dev] All Python Windows build

2011-03-10 Thread Jed Brown
As a related matter, it would be pretty cool to have configure run tests concurrently. It is silly that it takes more time to configure PETSc than it takes to build, that imbalance will get much worse as people get more cores on their development machines. I think cll is simple enough to easily exp

[petsc-dev] All Python Windows build

2011-03-10 Thread Jed Brown
On Thu, Mar 10, 2011 at 16:36, Barry Smith wrote: > Basically it is an attempt to totally refactor BuildSystem using everything > that was learned in the development of BuildSystem; it has no new ideas that > are not in BuildSystem it is just much simplier because all the paradgms are > already u

[petsc-dev] All Python Windows build

2011-03-10 Thread Barry Smith
On Mar 10, 2011, at 10:39 AM, Jed Brown wrote: > As a related matter, it would be pretty cool to have configure run tests > concurrently. It is silly that it takes more time to configure PETSc than it > takes to build, that imbalance will get much worse as people get more cores > on their deve

[petsc-dev] All Python Windows build

2011-03-10 Thread Barry Smith
On Mar 10, 2011, at 10:00 AM, Matthew Knepley wrote: > On Thu, Mar 10, 2011 at 9:36 AM, Barry Smith wrote: > > On Mar 10, 2011, at 9:01 AM, Satish Balay wrote: > > > python and win32fe are both cygwin dependencies and they are > > interlinked with cygwin PATHS, and UNIX style compiler usage. >

[petsc-dev] All Python Windows build

2011-03-10 Thread Barry Smith
On Mar 10, 2011, at 10:03 AM, Jed Brown wrote: > On Thu, Mar 10, 2011 at 16:36, Barry Smith wrote: > Basically it is an attempt to totally refactor BuildSystem using everything > that was learned in the development of BuildSystem; it has no new ideas that > are not in BuildSystem it is just mu

[petsc-dev] All Python Windows build

2011-03-10 Thread Matthew Knepley
On Thu, Mar 10, 2011 at 9:36 AM, Barry Smith wrote: > > On Mar 10, 2011, at 9:01 AM, Satish Balay wrote: > > > python and win32fe are both cygwin dependencies and they are > > interlinked with cygwin PATHS, and UNIX style compiler usage. > > > > Barry started to make fixes to configure to not use

[petsc-dev] All Python Windows build

2011-03-10 Thread Barry Smith
By the way this all runs cleanly on Windows using the Windows python and either Windows compilers or the Windows port of the gcc compilers. It also runs cleanly under cygwin (ignoring cygwins rebase, resource issues bugs). Barry On Mar 10, 2011, at 9:36 AM, Barry Smith wrote: > > On

[petsc-dev] All Python Windows build

2011-03-10 Thread Barry Smith
On Mar 10, 2011, at 9:01 AM, Satish Balay wrote: > python and win32fe are both cygwin dependencies and they are > interlinked with cygwin PATHS, and UNIX style compiler usage. > > Barry started to make fixes to configure to not use cygwin-python. But > I think the critical thing would be replaci