<div class="gmail_quote">On Sun, Nov 6, 2011 at 03:43, Dominik Szczerba <span dir="ltr"><<a href="mailto:dominik@itis.ethz.ch">dominik@itis.ethz.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div id=":zw">I am normally working and developing my codes on linux, only compiling<br>
them at the end for Windows, but need to evaluate the possibilities to<br>
also efficiently develop on Windows. Is anyone developing Petsc based<br>
applications on Windows and could share some experiences? In<br>
particular, is it possible to debug only on Cygwin's gdb port or also<br>
to use (somehow) the Visual Studio's built in debugger? Are there<br>
tools comparable to valgrind to detect MPI-aware illegal memory<br>
accesses and leaks? I heard about TotalView, but never worked with it.</div></blockquote></div><br><div>PETSc's configure writes a CMake file. You should be able to change the target to use visual studio. I haven't tested it, so it may need some minor tweaking, but it shouldn't be too hard.</div>
<div><br></div><div>None of the main PETSc developers run Windows. We are careful to write portable code and we test to make sure it works on Windows, but since we don't develop there, we don't get too frustrated with non-optimal aspects of the development environment on Windows. You are welcome to contribute improvements.</div>