I think I found the problem with sdl_gfx. I spotted a sequence of error messages that was preventing pygame2 from compiling. This was the first one:
In file included from src/sdlgfx/fpsmanager.c:23: > src/sdlgfx/pggfx.h:24:27: error: SDL_framerate.h: No such file or directory I solved it by making a symbolic link from /usr/local/include/SDL/SDL_framerate.h to src/sdlgfx. Then, I got one from the next file in /usr/local/include/SDL, which I fixed the same way. I thought that the SDL directory might be tripping up the installer, so I moved the files in /usr/local/include/SDL to /usr/local/include, and pygame2 compiled with no error messages.I just don't know how Marcus didn't encounter the same problem. On Sat, Aug 8, 2009 at 1:54 PM, Vicent Marti <tan...@gmail.com> wrote: > The exact location of the dynamic library is automatically located > when running the setup script. You might want to look at > 'config/config_modules.py' for the way each library gets automatically > located. > > Cheers, > Vicent Martà > http://www.bellverde.org > > > > On Sat, Aug 8, 2009 at 6:09 PM, Evan Kroske<e.kro...@gmail.com> wrote: > > Okay, I've got an unrelated question about changing the pygame > installation > > process. I'd like to know where exactly references to external libraries > are > > stored. Somewhere, a file must mention the exact location of the sdl_gfx > > shared object library file, but I can't find it. Am I missing some > crucial > > piece of information? > > > -- Evan Kroske http://welcome2obscurity.blogspot.com/ The code, comments, and challenges of a novice software developer desperate for attention.
