work areas, desirable features

[Michael]

I currently don't have access to MSVC 2015, but will try to get it.
I think if the program compiles with MSVC 2010, the step to MSVC 2015 should be a small one.
I will gather the changes that are needed for this and come back to you.

Have a nice weekend,
Michael

[thorsten]

I'm not sure but as I understand it the community editions are all free to use?

[thorsten]

By the way, I have no doubt that getting openEMS and its own close dependencies (CSXCAD) are easy to get compiled on MSVC. What kept me from trying are all the external dependencies like Qt, vtk, hdf5, cgal, boost, and so on that would have to be compiled all with the same MCVS. And vtk even with Qt support meaning to get them linked already at this stage...
I'm pretty sure that will be 95% of the work to get this going. But I may be wrong... Additionally of course I do not have any Windows machine, such that I really have a hard time even testing.

[Michael]

Okay, now I beginning to understand what you really need. You're right that's problem.

Do you want to implement the changes for MSVC support nonetheless?

Are you interested in reducing the need for external dependencies?
E.g. I think "boost" can be replaced quite easily.

[thorsten]

Well I would like to eventually get the python interface to work on Windows and as far as I see it that requires the MSVC compiled version...

E.g. I think "boost" can be replaced quite easily.

I would need to have another look at that, but if that would not be to difficult, sure why not.

Additionally cgal could also be one of those candidates. I pretty much only use it for the algorithm to test coordinates against triangulates surfaces...