Hi all,
As you can see from the linker error below the definition of SDL_UnLockSurface is not available to me. This is made all the stranger by the fact that SDL_LockSurface is!
Could someone pass their eyes over the command below and verify if I've got all the necessary linker flags present?
It would be much appreciated.
psp-gcc -I. -I/usr/local/pspdev/psp/sdk/include -O2 -G0 -Wall -I/usr/local/pspdev/psp/include/SDL -Dmain=SDL_main -D PSP_BUILD -D_PSP_FW_VERSION=150 -L. -L/usr/local/pspdev/psp/sdk/lib main.o entities/playerentity.o entities/platform.o collision/collision.o entities/entity.o animation/animationManager.o animation/spriteutils.o system/input.o system/screen.o ingameUI/viewport.o -lSDL_image -L/usr/local/pspdev/psp/lib -lSDLmain -lSDL -lm -L/usr/local/pspdev/psp/sdk/lib -lpspdebug -lpspgu -lpspctrl -lpspge -lpspdisplay -lpsphprm -lpspsdk -lpsprtc -lpspaudio -lc -lpspuser -lpsputility -lpspkernel -lpspdebug -lpspdisplay -lpspge -lpspctrl -lpspsdk -lc -lpspnet -lpspnet_inet -lpspnet_apctl -lpspnet_resolver -lpsputility -lpspuser -lpspkernel -o build/psp/simplePlatform.elf
animation/spriteutils.o: In function `SPR_YaxisReflectAndBlitSpriteTo':
spriteutils.c:(.text+0x580): undefined reference to `SDL_UnLockSurface'
SDL linking cannot find definition of Unlock Surface
...on my OSX is builds fine...svxs wrote:Is it a similar error message?
So there is no second error.
Code: Select all
int main(){
SetupCallbacks();
makeNiceGame();
sceKernelExitGame();
}
I see. I mistook the way he worded it to mean that his project compiled properly for OSX when using libraries and tools that are unrelated to the PSP, yet generated an unrelated compiling or linking error when being built for the PSP.
An odd issue if the OSX build is still erroneously letting the binary get linked to the improperly spelled function. No clue. Does it crash?
An odd issue if the OSX build is still erroneously letting the binary get linked to the improperly spelled function. No clue. Does it crash?
That's correct, OSX was compiling and running the improperly spelt function using an unrelated SDL implementation. My guess is that there is a typedef hidden in the OSX headers somewhere.svxs wrote:An odd issue if the OSX build is still erroneously letting the binary get linked to the improperly spelled function. No clue. Does it crash?
Any way, not the most important issue. I just wondered if anyone had encountred this.