On Sun, 17 Mar 2013, Barry Smith wrote: > > On Mar 17, 2013, at 5:59 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote: > > > On Sun, Mar 17, 2013 at 5:50 PM, Barry Smith <bsmith at mcs.anl.gov> wrote: > > > > Make a branch and fix any you find. It is not suppose to. > > > > I think this is a very tedious project and will probably have more > > stumbling blocks than path manipulation. > > > > If there is a machine where we can ssh to msys bash, then there might be a > > chance. > > > > I can't tell whether we would use GCC > > We would use the native Windows gnu compilers which use Window's paths. :-)
For one - there is no 'native Windows gnu compilers' that I'm aware of. But if you mean gnu compilers that don't need cygwin.dll - then I believe mingw compilers are also distributed as part of cygwin. [but I have not tired that] And if 'using Window's paths' is important - cygwin works with it aswell. [if our buildtools can manage that] >>>>> balay at Win7-KVM ~/junk $ ls c:\\cygwin\\home\\balay\\foo.h c:\cygwin\home\balay\foo.h balay at Win7-KVM ~/junk $ gcc -c vard.c vard.c:1:17: fatal error: foo.h: No such file or directory compilation terminated. balay at Win7-KVM ~/junk $ gcc -c vard.c -Ic:\\cygwin\\home\\balay balay at Win7-KVM ~/junk $ <<<<<<<<< But I think the primary concern here is 'remove cygwin dependency in our buildtool chain' I don't think msys is a solution for that. [And I suspect folks who want that solution don't don't even want to install ms-python or run configure with it] Satish
