gbadev.org forum archive

This is a read-only mirror of the content originally found on forum.gbadev.org (now offline), salvaged from Wayback machine copies. A new forum can be found here.

Coding > using MS Visual Studio NET 2003 as IDE?

#24061 - cochese - Tue Jul 27, 2004 8:00 am

Hi all,
I'd like to use VS NET 2003 as the IDE for writing stuff for the GBA and was wondering if somebody else uses it and has some plan on how to integrate a new language and build tools etc into it.
Thanks for any tips!
_________________
hiddenresource.corewatch.net - Aspects in Flash Game Development

#24063 - DiscoStew - Tue Jul 27, 2004 9:03 am

I used to work with VC 6 as my IDE with the GBA AppWizard, but the AppWizard isn't compatible with VS NET 2003 to my knowledge. Lucky for me, VS NET 2003 was able to convert my VC 6 project to the newer version with no problems.
With stuff from scratch or projects created non-VC6, I'm not quite sure other than perhaps adding a working MAK file to a Win32 console workspace that does all the compiler/linker/etc stuff and try from there.
_________________
DS - It's all about DiscoStew

#24076 - benjamin - Tue Jul 27, 2004 4:43 pm

Just use the BGScrollSample VC6 workspace from WntrMute and let VS.NET convert it. Then modify the make file and copy paste to suit your needs. Works fine for me so far.

#24135 - cochese - Wed Jul 28, 2004 11:13 am

Thanks alot bejamin! I will check it out!
_________________
hiddenresource.corewatch.net - Aspects in Flash Game Development

#24495 - gooms9 - Wed Aug 04, 2004 4:23 pm

What is so different in visual studio 2003 that wont allow you to compile gba games properly?

#24501 - DiscoStew - Wed Aug 04, 2004 5:53 pm

There is nothing different, you still run off a MAK file that directs the compiling of your code to a compiler that creates the GBA ROM (like DevKitAdv). VS 2003 is just one of those options to use as an IDE if you have it. I don't know how it is with other IDEs, but with VS 2003 (and VC++6 before), I'd get errors at compile-time, but unlike actual VC++ projects, I can't just double-click the error to direct me to that particular line. I have to open the file and search for the line that it had the error on, and then go from there.

For anyone who is having trouble getting VS2003 to work with a MAK file, I have something here that might help.

To use a MAK file, add the MAK file to your project (I usually add it through the right-click menu of the Project Name). Then go under your Project Name in the Solution Explorer and go into it's properties under it's right-click menu. IN the General tab under Configuration Properties, select Makefile. You could probably leave the Debugging tab alone. In the NMake tab, put "NMake /f *The_MAK_File*.mak in the first and second line, adding "/a" in the second.

That should be it. When making the ROM, use Build/Build Solution or Build/Rebuild Solution. Trying to use Debug/Start will not work, because you are using the MAK file.

NOTE: This is just for trying to get the MAK file usable, but in order for your project to compile with whatever compiler you are using, you'll need to make sure you have all the files required of it, like DevKitAdv uses crtbegin.o, crtend.o, crt0.s, and Linkscript. I don't know what the other compiler need.
_________________
DS - It's all about DiscoStew

#24502 - Miked0801 - Wed Aug 04, 2004 5:56 pm

There are utilities out there to fix the double click on error and take you there issue. Time to Google... :)

#24508 - pbmtp - Wed Aug 04, 2004 7:02 pm

The other solution is to use a standard makefile with a make command like the one provided in cygwin or msys

First add the path to make.exe to the tools path of vstudio: Menu (Tools/Options/Projects/VC++ Directories/Executable files)

Next: you create a "Makefile project"

Under nmake rules you can put the command that shall be used to build the project for example "make all"


in your makefile use a rule like this one to format the error messages from gcc format to VS one:


%.o: %.c
<TAB> $(CC) $(CFLAGS) -c $< -o $@ 2>&1 | sed 's/:\([0-9]\+\):/(\1) :/'


Hope this helps

Pb

#24547 - wintermute - Thu Aug 05, 2004 3:54 pm

Miked0801 wrote:
There are utilities out there to fix the double click on error and take you there issue. Time to Google... :)


devkitARM provides that all on it's own

#24548 - wintermute - Thu Aug 05, 2004 3:57 pm

pbmtp wrote:
The other solution is to use a standard makefile with a make command like the one provided in cygwin or msys

First add the path to make.exe to the tools path of vstudio: Menu (Tools/Options/Projects/VC++ Directories/Executable files)

Next: you create a "Makefile project"

Under nmake rules you can put the command that shall be used to build the project for example "make all"


in your makefile use a rule like this one to format the error messages from gcc format to VS one:


%.o: %.c
<TAB> $(CC) $(CFLAGS) -c $< -o $@ 2>&1 | sed 's/:\([0-9]\+\):/(\1) :/'


Hope this helps

Pb


nmake is just barely a step up from batch files where gcc is concerned. The best policy is to use gnu make.

The makefiles in the examples on http://ww.devkit.tk are fairly generic and reasonably well commented.

There's also a small section on setting up VS6 in the setting up section, a couple of pages in.

#24550 - wintermute - Thu Aug 05, 2004 3:58 pm

DiscoStew wrote:

NOTE: This is just for trying to get the MAK file usable, but in order for your project to compile with whatever compiler you are using, you'll need to make sure you have all the files required of it, like DevKitAdv uses crtbegin.o, crtend.o, crt0.s, and Linkscript. I don't know what the other compiler need.



devkitARM needs a specs switch when linking, that's it. No messing around with linkscripts and crt0, compile & go.