[libnds] Debugging in Visual Studio 2010

Post Reply
dornad
Posts: 5
Joined: Fri Dec 25, 2009 7:14 am

[libnds] Debugging in Visual Studio 2010

Post by dornad » Fri Jun 11, 2010 3:22 am

Hello everyone,

I'm trying to setup Visual Studio 2010 for libnds. I've followed the instructions for VS2008 in http://www.console-dev.de/2009/09/03/cr ... udio-2008/ with sucess up to the debugging section.

When I press F5, I see in the output that the compilation occurrs but I get the following error:

Image
"Parameter basePath cannot have zero length"

I've googled the basePath parameter but I've had no luck finding any reference to it, other than a OGRE problem, which was solved without any explanation.

Thanks.

elhobbs
Posts: 358
Joined: Thu Jul 02, 2009 1:19 pm

Re: [libnds] Debugging in Visual Studio 2010

Post by elhobbs » Fri Jun 11, 2010 5:47 pm

these instructions do not allow you to debug a program with Visual Studio - no matter the version. so, F5 will not work. Ctrl-F5 should work though - this is just launching the target - in this case in an emulator.

dornad
Posts: 5
Joined: Fri Dec 25, 2009 7:14 am

Re: [libnds] Debugging in Visual Studio 2010

Post by dornad » Tue Jun 15, 2010 3:26 am

elhobbs,

Control+F5 produces the same basePath error. Any ideas?

Thanks!

elhobbs
Posts: 358
Joined: Thu Jul 02, 2009 1:19 pm

Re: [libnds] Debugging in Visual Studio 2010

Post by elhobbs » Tue Jun 15, 2010 1:30 pm

dornad wrote:elhobbs,

Control+F5 produces the same basePath error. Any ideas?

Thanks!
how about a screen shot of the Debugging properties window from the project properties?

dornad
Posts: 5
Joined: Fri Dec 25, 2009 7:14 am

Re: [libnds] Debugging in Visual Studio 2010

Post by dornad » Thu Jun 17, 2010 12:46 am

elhobbs,

Here you go. Thank you!

Image

calvinss4
Posts: 1
Joined: Sat Nov 14, 2009 6:28 am

Re: [libnds] Debugging in Visual Studio 2010

Post by calvinss4 » Mon Sep 27, 2010 9:02 am

I ran into the exact same problem when migrating from 2008 to 2010. I still don't know what exactly causes the problem, but there's an easy workaround. Just specify the full path to your make executable, i.e.
project Properties -> Debugging -> Command -> c:\devkitPro\msys\bin\make

Post Reply

Who is online

Users browsing this forum: Ahrefs [Bot] and 1 guest