If it's on openGL you won't have too much problem, as I believe OpenGL works in a similar way DevkitPro video API does, IF:
The original system requirements are below the DS's (DS has 4MB RAM and 2 cores of 67 and 33 MHZ, but it has the advantage: an aplication takes over the DS when started, so every resource is yours)
You know how the program works by looking at the source. What functions it uses and such.
You know how openGL works or at least how the functions of openGL the program uses work.
You know the tarjget's system, by that I mean equivalent functions to what the program uses on the original platform.
And, of course, you need to be patient.
I think a porting project it's too much as your fist project since you have to know the original platform and the target's. Anyway, understanding other people's sources is a bit tricky, because everyone has their style, but it's a good ability to have.
C is also a difficult language to start with, but once understand it you'll discover that every language works in a similar way.
Thank you for your words.
It turns out the program I was looking at utilizes mabye 64MB of ram and a Pentium 2 processor. Although the readme says even less is needed as it will skip frames on slower computers. Is this a lost cause?
Thanks for the step by step listing of things to understand before I rewrite the code. I am diligent on learning C for reasons like you mentioned, along with my
favourite coder's reasons.
QUOTEPeople will tell you that C is old and hard to program, but that is sort of the point. Your goal shouldn't be to make something quick but rather to learn the basics. C is a small but incredibly powerful language that you will never grow out of, so learn it well rather then constantly try to find a different language that is easier.
@
BigOnYa:
@
Psionic Roshambo:
@
HiradeGirl:
@
Veho:
