No Info for Building on Windows

[Malkierian]

There's nothing in the README about it, and when I try to cmake in the root directory with the CMakeLists.txt in it, it detects for Visual Studio 2010 (though I don't know how to switch that to 2012), but I get several errors:

http://pastebin.com/ugiwwLxf

And yeah, the Windows backend doesn't exist...

[Malkierian]

Also, I just wanted to say the reason I came here is because C++, I believe, while not being as flexible as Java, provides for quite a bit more security, as you can't decompile it. I don't care about having to build it myself, but not having it available for building on Windows kind of puts a damper on that.

[scooterman]

Hi @Malkerian,

thanks for the interest, but unfortunately there's no windows backend,
hence its disappearance on README and the source itself. It's on my todo
list after I finish with the emscripten backend, though.

Victor

2013/6/17 Malkierian notifications@github.com

There's nothing in the README about it, and when I try to cmake in the
root directory with the CMakeLists.txt in it, it detects for Visual Studio
2010 (though I don't know how to switch that to 2012), but I get several
errors:

http://pastebin.com/ugiwwLxf

And yeah, the Windows backend doesn't exist...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/40
.

[scooterman]

We accept contributions, though :)

2013/6/17 Victor Vicente de Carvalho victor.v.carvalho@gmail.com

Hi @Malkerian,

thanks for the interest, but unfortunately there's no windows backend,
hence its disappearance on README and the source itself. It's on my todo
list after I finish with the emscripten backend, though.

Victor

2013/6/17 Malkierian notifications@github.com

There's nothing in the README about it, and when I try to cmake in the
root directory with the CMakeLists.txt in it, it detects for Visual Studio
2010 (though I don't know how to switch that to 2012), but I get several
errors:

http://pastebin.com/ugiwwLxf

And yeah, the Windows backend doesn't exist...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/40
.