The GP2X is based around the MMSP2 System on Chip, which means the CPU and just about everything else is built into one unit. A better CPU would mean getting rid of the MMSP2 and using a different SoC, not just swapping one little processor for a slightly faster one.
As far as homebrew goes, I've been doing that all my life as a hobby with no intention to ever get into the games industry (I've seen what it does to people after a couple of years). Got a CS degree, then happened to fall into a multimedia job shortly afterwards. Did a mixture of web and...
Dp, down etc are stick directions not buttons so the user won't need to confirm them, but other buttons are just numbered and I don't think it's possible to tell what's mapped to what without asking the user.
Why should a new purchaser have to mod their device the moment they get it. It might be easy for you to add a dpad but it's not for more people. The touchscreen was probably added because it was cheaper and easier to source than a non touch, not because they wanted to add new features. And SDHC...
Craigix (with an i before the x - don't leave it out unless you really want to piss him off) is a person not a thing, so I imagine he'd find it pretty hard to develop himself. Or to put it another way, what on earth are you going on about?
As far as I'm aware they haven't even decided on a chipset for the new machine yet, so if you start a 2-3 month software development now I can see you finishing a few months ahead of the machine you intend to test on :). Might be a better idea to do something in SDL targetting the gp2x, then...
What does the language have to do with game programming? If you can code, then you can code. The language shouldn't matter (unless you're going from procedural to functional languages or something else equally strange).
I got into game programming by reading the Input magazines in the 80s when...
Whatever you do, don't put the uboot img back on there again. It's not necessary (I'm pretty certain it's the same version for 2 as it is for 3) and that is the part that is most likely to cause a brick. As long as uboot is still intact then you've got a chance of sorting things out without...
-L/opt/open2x/gcc-4.1.1-glibc-2.3.6/include is telling the linker to look for libs in the include directory. This should be pointing to a libs directory instead.
What exactly are you trying to do? You're using i386 gcc, but gp2x arm compiled libs (/opt/open2x/gcc-4.1.1-glibc-2.3.6/lib). If you want a gp2x executable you need to use an arm version of gcc, but if you want an i386 linux executable you need i386 libs.
CC = gcc
Chances are you're using the standard i386 gcc not the gp2x arm version. Make sure the path to gcc and it's name are correct. Same goes for things like g++ and ld.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.