Well, I tried what you said, and tried a clean install, urpmi has to be run
from root :P. Anyway, same thing happened. I was getting a little tired of
this, so i went to usr/lib/libSDL.a and looked at it. Does it have to be
extracted or something? Because it gives me the option too. All the
functions the compiliing error refers to are there. I was thinking, maybe I
just don’t have access. libSDL.a is a read-only file with permission from
the root. I tried compiling from root, but to no avail. Am I supposed to
extract it?
///////////
// Leo //
///////////_________________________________________________________________
Get holiday tips for festive fun.
http://special.msn.com/network/happyholidays.armx
Leo . wrote:
Well, I tried what you said, and tried a clean install, urpmi has to
be run from root :P. Anyway, same thing happened. I was getting a
little tired of this, so i went to usr/lib/libSDL.a and looked at it.
Does it have to be extracted or something? Because it gives me the
option too. All the functions the compiliing error refers to are
there. I was thinking, maybe I just don’t have access. libSDL.a is a
read-only file with permission from the root.
libSDL.a is the static library (because its name ends with “.a”).
Usually people use the dynamic library (ending in “.so”). Using the
static library will include a full SDL in your program and increase its
size, and often leads to various linking problems. Using a dynamic
library on the other hand, allows sharing the code between multiple SDL
programs, and gives a convenient way for your users to upgrade their SDL.
I tried compiling from root, but to no avail. Am I supposed to
extract it?
No, you’re not supposed to extract a .a before using it. Anyway, if
you’re just beggining, don’t use the static libraries yet.
Now, about .so files : the dynamic SDL library version is probably
/usr/lib/libSDL-1.2.so.0
Using sdl-config to compile your program will use the dynamic version.
Stephane