GP2X Development Tools

[Pickle]

So it appears that I can write applications using either using the offical SDK or i can use the devkitGP2X that is devoped by other users (I would use it with VC++ as the IDE).

Any benefits of one over the other? Or is there even a better way?

 

[crusty]

So it appears that I can write applications using either using the offical SDK or i can use the devkitGP2X that is devoped by other users (I would use it with VC++ as the IDE).

Any benefits of one over the other? Or is there even a better way?

Here's my list, others might have different opinions:

Official SDK

Pros:
1. Uses DevC++ integrated development environment.
2. Includes linux version 1.2.25 headers and libraries.
3. Can be used for -shared or -static image creation.
4. Includes MS-Windows compiler for testing SDL code.

Cons:
1. Uses DevC++ integrated development environment.


devkitGP2X

Pros:
1. Use whatever environment you choose.
2. Includes a more recent version of GCC (smaller faster executables).
3. Alternate hardware libraries are being developed by the community.

Cons:
1. Requires -static image creation.
2. Requires that executables be moved to gp2x for all debugging.

 

[yaustar]

Just to clear up:
The Cons for DevKitGP2X also apply to the official SDK.

You can compile using -shared with the standard SDL libraries but not with later HW-accelrated (I think). You can easily compile the SDL apps for Windows using MinGW or any standard Windows Compiler with any environment.

The main advantage of the official SDK is that is easier to setup.

If you are going to use VC++ as the IDE, then go with DevKitGP2X.
http://wiki.gp2x.org/wiki/Using_Visual_C_2...Express_Edition

 

[Pickle]

Just to clear up:
The Cons for DevKitGP2X also apply to the official SDK.

You can compile using -shared with the standard SDL libraries but not with later HW-accelrated (I think). You can easily compile the SDL apps for Windows using MinGW or any standard Windows Compiler with any environment.

The main advantage of the official SDK is that is easier to setup.

If you are going to use VC++ as the IDE, then go with DevKitGP2X.
http://wiki.gp2x.org/wiki/Using_Visual_C_2...Express_Edition

Well I have the offical SDK set up (all i did was extract) and I have ran a basic app in windows.
I like that I can very easily switch from windows to GP2X with one setting.

 

[yaustar]

I do the same in Codeblocks with MinGW and DevkitGP2X. The only real advantage of the official SDK is that it is all ready to go from the start but the functionality can still be acheived via manual setup.

 

[Parkydr]

Here's my IDE

I sometimes use xemacs as well

 

[Artemio]

Vi rules!

I use the same IDE ^^ Although I am using oppo's toolchain. I'll try devkitGP2x again and see how I feel with it. I believe that the options are not well documented anywhere, we could update teh wi,ki if enough information is gathered.

 

[luteijn]

Almost the same as my IDE...
Since it's vim (unless you've deliberately changed the titlebar), you might want to consider using ":syntax on" to make it colorize things according to the syntax.

P.

 

[Parkydr]

Almost the same as my IDE...
Since it's vim (unless you've deliberately changed the titlebar), you might want to consider using ":syntax on" to make it colorize things according to the syntax.

P.

It's just vim, rather tham gvim, running from the command line in a KDE Konsole window. I just use it for a bit of quick hacking.

If I'm doing something a bit more complicated, involving several files, I use xemacs which has syntax highlighting, multiple file search and make facilities but doesn't take over the whole desktop like a full IDE.

 

[luteijn]

It's just vim, rather tham gvim, running from the command line in a KDE Konsole window. I just use it for a bit of quick hacking.

I just installed konsole for a little test, and it looks like it supports kolor for plain vim just fine:



P.