Xmoto for PSP

[jandujar]

I'm waiting for weeks to see xmoto for PSP.

I hope you finish the port.

Are you porting the latest 0.31? It uses SDL for graphics

[parkermauney]

Wow, 0.3.1's already out?

He's porting 0.2.7.

[gambiting]

Wow, 0.3.1's already out?

He's porting 0.2.7.

When I started the newest version availiable from sourceforge was 0.2.7.I will check out this 0.3.1 today.

[parkermauney]

Won't you have to restart all your coding though?

Did 0.2.7 not use sdl for graphics?

[jandujar]

why don't you tell us the modifications you done. Maybe we can help you.

[gambiting]

why don't you tell us the modifications you done. Maybe we can help you.

Modifications done in code itself are very minimal - I have only hardcoded few variables,that could not be resolved from psp os,like GAMEDATADIR - it's hardcoded to "ms0:/PSP/GAME/XMOTO/".I mainly focused on building Makefile to force the code to compile,in whatever state it is.I can't find bug that causes Xmoto to stop on psp by reading source code,as it wasn't me who made it.It would take weeks before I would be able to understand the code as my own.It's simplier to build it as is,and then debug it to find where exactly it stops,and then eliminate the problem.Most of the time before succesfull compilation I've spend on looking for libriaries and resolving various linking problems,not reading the code.And don't worry,I'm still working on it,and I don't plan to abandon it anytime soon.If you need any info just ask.

[parkermauney]

So, when errors come up, you can use a debugger to find exactly where the error is? Like the lua debugger?

[gambiting]

So, when errors come up, you can use a debugger to find exactly where the error is? Like the lua debugger?

No - Lua is interpreted language,and C is compiled.That means that in LUA you can see exactly where the error is,while in C you can see only assembly code with that error.Depending on that,you can't find the exact place in source code in C.You have to find out what errror means,rather than where it is.

[parkermauney]

OK, I figured that after seeing screens of psplink.

How do you decipher the problem from hex codes though?

[gambiting]

OK, I figured that after seeing screens of psplink.

How do you decipher the problem from hex codes though?

I don't read straight from hex codes - first debbuger shows me clean assembler code,and values of variables in hex codes.Of course gdb can convert them to normal values,so I can read them.By doing so,I can see what's wrong in debbuged program when it crashes - for example: program stops,when some variable value is "c:\xmoto_logo.png".It's clear that using such path in psp program is impossible,so I will have to find it in real code and change to "ms0:\psp\Xmoto\xmoto_logo.png".But normally things are not that easy