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 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. 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. 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. I'm looking forward to your opinions and answers. Best regards, Albert
_______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
