Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Visual Fucking Studio

Name: Anonymous 2010-01-02 22:02

What the fuck is the deal with Visual Studio? I've been writing a small game using OpenGL and GLFW in Ubuntu, expecting it to be fairly easy to make it compile on Windows. I was stuck in Windows today (encoding a few DVDs, can't be arsed to find Linux equivalent software) so I figure why not do the port?

What a fucking nightmare this has been. Several gigs to download and install VS Express with Windows SDK. I couldn't get my pre-build script to run, so I gave up and just do it manually each time in a terminal. Adding the project files to git required me to turn off some of the patch validation. It refused to compile two .c files with the same name in different folders; I fought with it for hours before just fucking renaming one of them. It doesn't come with OpenGL extensions, nor can you include them normally; you have to wglGetProcAddress every fucking function you want to call. It absolutely refuses to link glfw statically; I had to use GLFW_DLL, which the documentation recommends not to do.

And now that I finally have the fucking thing compiling (and it actually does work), I can't see any log printouts. printf() successfully returns the number of characters printed, and the output goes... nowhere? I've got this Output widget in the IDE, which lets me select between Build, Build Order, and Debug, none of which contain my prints, to neither stdout or stderr. What the fuck?

And after all this, you know what? I've had to make almost no code changes to get it to work (glext, WinMain() and a few missing C99 features). It's not the code that's the problem, it's the goddamn development platform.

Do any of you /prog/riders actually like coding with VS on Windows? If so, what the fuck is wrong with you?

Name: Anonymous 2010-01-03 17:13

>>14
I don't see how Niggers and beagles are related.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List