DevkitARM: Differences in compiled code Mac OS X vs Windows

support for the ARM toolchain
Post Reply
WinterMute
Site Admin
Posts: 1845
Joined: Tue Aug 09, 2005 3:21 am
Location: UK
Contact:

Re: DevkitARM: Differences in compiled code Mac OS X vs Windows

Post by WinterMute » Sun Jan 17, 2010 2:22 am

What happens with r27?
Help keep devkitPro toolchains free, Donate today

Personal Blog

WinterMute
Site Admin
Posts: 1845
Joined: Tue Aug 09, 2005 3:21 am
Location: UK
Contact:

Re: DevkitARM: Differences in compiled code Mac OS X vs Windows

Post by WinterMute » Tue Jan 19, 2010 2:39 pm

Why are you getting C++ name mangling in a compiled C file?
Help keep devkitPro toolchains free, Donate today

Personal Blog

WinterMute
Site Admin
Posts: 1845
Joined: Tue Aug 09, 2005 3:21 am
Location: UK
Contact:

Re: DevkitARM: Differences in compiled code Mac OS X vs Windows

Post by WinterMute » Wed Jan 20, 2010 4:00 pm

It's probably best to use .c for C files & .cpp for C++ to avoid confusion. I don't think it's related to your problem since you explicitly use g++ for compiling & linking though.

I really don't know what the issue is unfortunately, could you host the project somewhere & let me have a look. It's been a while since I worked with gp32 though so I'm not sure I'll be able to help. Are you using libmirko or the gamepark libs? If it's the latter then I'll need to find a set of those somewhere too.
Help keep devkitPro toolchains free, Donate today

Personal Blog

WinterMute
Site Admin
Posts: 1845
Joined: Tue Aug 09, 2005 3:21 am
Location: UK
Contact:

Re: DevkitARM: Differences in compiled code Mac OS X vs Windows

Post by WinterMute » Wed Jan 27, 2010 10:39 pm

did you get anywhere with this? I'm in the middle of sorting out devkitARM r28, would be nice to get this sorted if it's a problem on my end.
Help keep devkitPro toolchains free, Donate today

Personal Blog

Post Reply

Who is online

Users browsing this forum: No registered users and 13 guests