On Thu, 30 Jul 2015 08:03:25 +0000 "Garth N. Wells" <gn...@cam.ac.uk> wrote:
> On Wed, 29 Jul 2015 at 19:21 Albert Ziegenhagel < > albert.ziegenha...@scai.fraunhofer.de> wrote: > > > Hi everyone, > > > > > > > > I managed to build Dolfin 1.5 on Windows using Visual Studio > > including the (in my opinion) most important dependencies like > > Trilinos and PETSc. I recommend rebasing your changes to development version - master branches of all FEniCS packages. Of course you can backport your changes into latest release and publish it by yourself. But we don't currently have maintenance branch and we will not patch previous releases. Jan > > > > > Well done, I don't imagine it was easy. > > > > > > > > I had to apply only minor changes to the Dolfin C++ source code and > > to the CMake build files. Additionally I had to make some changes > > to the python code that calls the form compiler. > > > > > > > > I suggest making pull requests in small chunks. > > Now the last problem I seem to face is that Visual C++ has a limit > for file > > paths of 260 characters. Because of the (quite long) hash > > signatures that are included multiple times in the path to the > > build directories this limit is exceeded and the Visual C++ > > compiler is failing to compile the forms. In my opinion it would be > > sufficient to include the hash signature only once in the path (in > > the name of the cache directory) and not additionally in the names > > of the source files and projects. This would dramatically reduce > > the length of paths Visual C++ has to deal with and should be > > sufficient to make it work. > > > > > > > > Good point. We could work on reducing the path length. > > > > Now my question is whether there is enough interest within the > > FEniCS development team to assist me in applying the necessary > > changes. In return I’m definitely willing to contribute my changes > > back to the project, verifying all the tests that come with FEniCS > > and ensure that the Windows compatibility stays up to date in > > coming releases. > > > > > > > > We'd be happy to accept changes. Maintenance is an issue because no > developers and very few users use WIndows. Also, we also don't have > buildbot coverage for Windows so it will take some community effort > to keep Windows builds working. It would be great if you're willing > to do this. > > Garth > > > > > I’m looking forward to your opinions and answers. > > > > > > > > Best regards, > > > > Albert > > _______________________________________________ > > fenics mailing list > > fenics@fenicsproject.org > > http://fenicsproject.org/mailman/listinfo/fenics > > _______________________________________________ fenics mailing list fenics@fenicsproject.org http://fenicsproject.org/mailman/listinfo/fenics
