Visual Studio - output *.nds (won't load into external prog)

[spindulik]

My apologies if this question is not at the correct forum.

I integrated Visual Studio 2008 Express with DevkitPro as described at
bogus url removed
Very carefully followed the instructions. Re-installed several times and many hours of Google searching for answers.

With success of creating the *.NDS file that actually works!!!! I have not been able to make Visual Studio capable of executing the NDS file with an external program, such as "c:\desmume\desmume.exe" (note the short file names and directory are compliant). I have to manually run the DS Emulator to test my NDS files from my project folder.

My project is also short file names and directory at the root of the "c\" directory of my HDD.

Here's the error window that I get from my Visual Studio program:

-----------------------
Microsoft Visual Studio
Unable to start program 'c:\VisualCPP\PADemo\PADemo\Release\PADemo.nds'
The specified file is not recognized or unsupported binary format.
-----------------------

[Alriightyman]

Not sure if it will work for you, but what I did was go under the 'project' menu, click '(project name) properties'.
When the window opens, go under 'Configuration Properties', then cllick 'Debugging'. On the right side, Under 'Command', click the dropdown tag and select 'browse'. Find your emulator, and select it. Then go under 'Command Arguments' and delete the bit at the beginning so it only shows

Code: Select all

$(TargetPath)

Click ok and it should work. At least it did for me.
I should also add that my devkitpro and visual studio stuff is under D:\ not C:\.... So I can't guarantee it will work.

[WinterMute]

Sorry, PAlib is not supported here.

http://wiki.devkitpro.org/index.php/PAlib

[spindulik]

Not sure if it will work for you, but what I did was go under the 'project' menu, click '(project name) properties'.
When the window opens, go under 'Configuration Properties', then cllick 'Debugging'. On the right side, Under 'Command', click the dropdown tag and select 'browse'. Find your emulator, and select it. Then go under 'Command Arguments' and delete the bit at the beginning so it only shows

Code: Select all

$(TargetPath)

Click ok and it should work. At least it did for me.
I should also add that my devkitpro and visual studio stuff is under D:\ not C:\.... So I can't guarantee it will work.

Thanks a lot!
This makes life easier. I have done programming C/C++ for a few years, but that was until 5 years ago. I have forgotten a lot since then, and some things have changed, it appears.

"PAlib is not supported here". What's up with that, got some sort of grudge going on here?

[Discostew]

"PAlib is not supported here". What's up with that, got some sort of grudge going on here?

Making the tools used for homebrew programming more accessible to a wider range of skillsets is a laudable goal - one that is shared wholeheartedly by devkitPro. Unfortunately PAlib has not kept pace with the toolchain and library releases from devkitPro, resulting in a situation where users are being advised to replace the latest releases with old binaries which are no longer supported. For this reason devkitPro will not provide support to users attempting to get PAlib working.

[spindulik]

Making the tools... ...Unfortunately PAlib has not kept pace...

[/quote]

I see. I have customized Visual C/C++ to be directly associated with DevKitPro, and associated files. All things appear to work well so far.

I have done some reading about the architecture of the DS and how different software resources are allocated to the hardware. Quite unlike programming for a PC, where all I have to do is dive in and start being creative, not worring about hardware so much.

Thanks again for your help and information.

[Sylus101]

*Not intending on starting anything... just adding a comment*

You should absolutely go to setup questions regarding PALib to it's own forum. Wintermute directing there is the right way to go.

Yes, there was an issue for a very long time where PALib users were being told to use older version of the devkitPro toolchain and that was not a good thing. Quite recently though, PALib was brought up to speed and does currently work with current the current release of devkitARM and libnds.

[vuurrobin]

You should absolutely go to setup questions regarding PALib to it's own forum.

except that the palib forums currently doesn't work...

[WinterMute]

And currently working isn't the same thing as will be working in the future. It took 3 years for PAlib to get to the state where it's capable of working without destroying the tools it depends on to work, how long will it take when it breaks again?

The main PAlib website is in a state of disrepair, there appear to be no regular maintainers and distribution appears to be a random collection of rapidshare links posted by random users. Why would I send people there when I know from personal experience over the last few years that they'll get bad advice and end up starting over from scratch when they find they've outgrown PA_ functions?

[Sylus101]

No need to really head down that road... I do tend to share those feelings...