Jump to content

  • Log In with Google      Sign In   
  • Create Account

Awesome job so far everyone! Please give us your feedback on how our article efforts are going. We still need more finished articles for our May contest theme: Remake the Classics

#Actualdougbinks

Posted 07 January 2013 - 03:56 AM

[Edited as miss-read some of the original post]

Do you have the call stack from the debug session of what happened when trying to run the example - I've run this on several computers with no problems so it might be something simple for me to fix if I can get enough information.

#2dougbinks

Posted 07 January 2013 - 03:56 AM

[Edited as miss-read some of the original post]

Do you have the call stack from the debug session of what happened when trying to run the example - I've run this on several computers with no problems so it might be something simple for me to fix if I can get enough information.

#1dougbinks

Posted 06 January 2013 - 05:13 PM

"Unable to start application
C:\blablabla\glewfw\debug\glewfw.dll"

 

Hi Dakattack - this was explained briefly in the post I made, but I'll expand further.

 

You need to set the 'example' project as the startup project. This is done by right clicking on the project and choosing 'Set as StartUp Project'. The example will then run, rather than the dll (you can't run a dll on it's own).

 

Note that you need to do this because the MS decided to put the startup project as a user defined setting which isn't normally included in a version control system (this makes sense in some scenarios, but why on earth it can even select a dll over an exe is beyond me).

 

Good luck with this, but I'd also advise doing some basic tutorials for Visual Studio and C or C++ programming to get more familiar with the toolset and compilation / linking issues.


PARTNERS