devkitPro

Hi all!

Hope that anybody still uses these forums regarding gp32 development... I usually posted doubts in the mailing list but i wasnt aware of the forums...

I have been trying to make some developments for the gp32 during the pasts years and i am very grateful to the tools that dkpro provides... Recently i have succeded on building the latest toolchain on my Vista, however i applied some modifications:
- gcc-4.3.2 (no diffs applied)
- patched newlib adding a subset of pthreads ( appliying the diffs from the gp32 FreeSCI project - http://www.retrovg.com/gp32/)
- modified libstdc++-v3 to support the pthread subset (hardly patched )...

If i understood correctly there is no official support for a modified buildscript, but i would appreciatte if anybody could give me some suggestions about debugging:
I am trying to setup an environment with debug symbols for newlib (on my setup i am using an usb cable with a gdb stub to debug on hardware) but i found that all the libs in the dkarm environment are already stripped... Is there a way to build the enviroment with debug symbols active?
Also i would like to apply some modifications to gp32_crt0.s however i cannot inspect the code from insight of this file... I dont know exactly if i have to modify the .specs file or link a new crt0...

Any suggestion is welcome

Regards

@B^)>

P.S: Apologies if my english is strange, i am from spain

kidchaos2k8 wrote:Hi all!

I have been trying to make some developments for the gp32 during the pasts years and i am very grateful to the tools that dkpro provides... Recently i have succeded on building the latest toolchain on my Vista, however i applied some modifications:
- gcc-4.3.2 (no diffs applied)
- patched newlib adding a subset of pthreads ( appliying the diffs from the gp32 FreeSCI project - http://www.retrovg.com/gp32/)
- modified libstdc++-v3 to support the pthread subset (hardly patched )...

The ARM toolset has now been updated to 4.3.2 anyway. The pthreads patches look a little dodgy to me being honest - there are patches to areas of newlib which aren't built or used by devkitARM. I'm a little concerned about the impact that kind of thing might cause on the other targets but do feel free to experiment for your own use.

I am trying to setup an environment with debug symbols for newlib (on my setup i am using an usb cable with a gdb stub to debug on hardware) but i found that all the libs in the dkarm environment are already stripped... Is there a way to build the enviroment with debug symbols active?

comment out the bit in the script that strips the installed binaries, it's down at the bottom of build-devkit.sh

Also i would like to apply some modifications to gp32_crt0.s however i cannot inspect the code from insight of this file... I dont know exactly if i have to modify the .specs file or link a new crt0...

The gp32_crt0.s is distributed along with devkitARM for easy modification, it's in <path/to/devkitARM>/arm-eabi/lib - run make CRT=gba32 in that folder to rebuld the arm & thumb variants.