I’m interested in beginning to develop Virtual Boy games. I successfully got David Tucker’s V810 GCC 2.95 compiler installed. I couldn’t figure out what set of command line commands to get a program ready for use on the Virtual Boy. Could somebody provide me with a simple set of commands to get a program compiled for use on the Virtual Boy?
I attempted to look at the VB Development Wiki, but the simple tutorials have broken links.
The commands I used to compile MrSparkle’s Chrono Trigger Run demo wwere something like the following.
v810-gcc -c main.cpp -o main.elf -mv810
objcopy main.elf demo.vb
No offence, but, did you try searching the forum for “makefile”? 😉
I think the info might be on the wiki, too… (If not, it should be :-P)
Also, welcome to the VB dev. scene! 😀
If you don’t understand something, make sure to check the wiki, search the forums, and then ask questions. 😉
C’mon RunnerPack, don’t be so harsh 😛
IMO, that makefile is a huge overkill for someone that just wants to compile some simple demo code.
fobbio, just use the two simple commands provided by David Tucker in the build.txt file:
//to build a project
v810-gcc -O -I. *.c -o test.elf
v810-objcopy -O binary test.elf test.vb
Thank you both kindly for your help.
RunnerPack, I did try to find it on my own. I downloaded the source code for some of the homebrew games to see if I could find something there, but couldn’t get it working.
DanB, Thanks a lot, that’s just I was hoping for in simplicity.
I couldn’t get it working, so I went to GCCVB and am using the make.bat with success so far.
- This reply was modified 12 years, 3 months ago by vbman.
I’m glad to hear you got it working, fobbio! Have you made anything with it yet?
Too bad you can’t use the cygwin-hosted one. Care to go into detail about the problem(s) you had?
I’ve started adding automatic “grit” graphics compiling to the makefile jorgeche posted (with automatic handling of .S assembly files as a bonus side-effect) but there are still some “issues” to resolve. No idea when (if) I’ll get back to it, though… Hard to find time for VB stuff these days, as I’m sure everyone can attest to…
If you can type “make” and it builds your project, it’s just as much “kill” as you need. If, on the other hand, you use the “underkill” approach and your project becomes more than that simple system allows (as in, you add one source file :-P) it just means more work implementing the makefile you should have used from the beginning…
Besides, you just download the file, drop it in your project directory, and edit the “TARGET” define. It’s not like it has to be completely rewritten each time you want to use it. Isn’t that what “make” was made for in the first place? 😛
If you’re completely new to linux and makefiles, it’s not a bad idea to start small with a script you can actually understand and go from there…
Plus, that simple script can handle more than one source file. That’s what the *.c is for, you know 😉
It’s not that I’m against makefiles, I’m just saying that writing a makefile with only those two lines can be a good start.