[CMake] Figuring out dependencies for a library in order to build

[E. Wing]

SDL is quite a bit more mature and more heavily used than SDL_sound so
I think they got all the autoconf stuff working. But there has been
some griping in the Unix -side of the OS X community because the
framework distribution we do doesn't include the sdl-config script.
Windows users I don't think even care. But the truth is with SDL, the
dependencies are pretty simple and predictable, so you generally can
do without one. So figuring out the SDL dependencies is doable (I
hope). I just submitted an improved FindSDL.cmake module (and friends)
which might be in CVS now. I have tested it on Debian, Fedora Core,
FreeBSD, SuSE, Windows MinGW, Visual Studio, and OS X. So far SDL has
been predictable enough that I didn't need it. (But maybe you can
break it?)

SDL_sound on the other hand is not predictable because it can be
compiled in too many different ways with many different dependencies,
which are independent of platform.

If you do find a problem in my FindSDL.cmake module though, please let me know.

Thanks,
Eric


On 7/18/05, Amitha Perera <perera at cs.rpi.edu> wrote:
> On Mon 18 Jul 2005, E. Wing wrote:
> > On 7/18/05, William A. Hoffman <billlist at nycap.rr.com> wrote:
> > > For example wx windows has a script wx-config that tells you what
> > > flags and libraries to link.  How are users of the SDL_sound
> > > supposed to do this stuff without CMake?
> >
> > Currently, there is no configuration file like wx-config as far as I
> > know.
> 
> For what it's worth, SDL itself does have such a config, at least on
> my RedHat system:
> 
> $ sdl-config --libs
> -L/usr/lib -Wl,-rpath,/usr/lib -lSDL -lpthread
> 
> I don't know anything about SDL_sound, and very little about SDL, so
> I'll go back to lurking now.
> 
> Amitha.
>