[OpenWalnut-Dev] There is a decision to be made

[Alexander Wiebel]

Hi List,
here comes my comment to Sebastian's statement on the state of the
VisualStudio port.

Sebastian is definitely right in that the code is not in a good state
regarding VisualStudio compilationat the moment. It is also true that I
did not do much in this direction. However, I think that this is the
case mainly due to the one main Problem with templates that stopped my
work on the code. I think that the time needed to maintain the Visual
Studio support is not too high as soon as someone (hopefully I) gets the
template code running.
As soon as this is the case, I believe that reacting only to the
incremental changes should not be such a big problem. And as I am
working with VisualStudio now all the time, it does not cost me too much
effort to test the port again and again. It would be just in my very
personal interest.

In case we can not find a solution or workaround for the template stuff,
I have to agree with Sebastian, that VisualStudio support is not in
reach soon and that (in this case) the code regarding VisualStudio
should be removed.

Finally, I definitely agree to remove the hints to VisualStudio from the
website in the current state (I can do this fast).

Cheers

Alex

On 11/29/2011 12:36 PM, Sebastian Eichelbaum wrote:
> Hi List
> 
> There is this little ticket #39 - Visual Studio does not compile WMatrixFixed ... And I am quite sure there are much mure code parts which will not work currently (for example these ugly export declaration stuff). We have several code parts and CMake specifics for VIsual Studio which never have been documented properly nor do we know whether they are needed or not.
> 
> Fact is:
> 
> * we currently not compile on Visual Studio (for some months now!)
> * we claim to compile on Visual Studio
> 
> I know that Alex wanted to manage the Visual Studio port but of course his time is limited. The time needed to continuously maintain the Visual Studio compatibility is too high. We will not be able to maintain this. This is why we drop Visual Studio support officially. I will remove the Visual Studio specific codes on December 31rd.
> 
> To re-introduce Visual Studio support, we need more than a quick hack which compiles the code. We need documented and clearly emphasized Visual Studio specific codes. We need to minimize the amount of VS specific code, because I am very sure that much of the VS specifics we currently have are not really needed. Besides this, we need a maintainer, who has the time capacity to maintain it! 
> 
> Bye
> Sebastian
>