SDL driver development run-around time

Hi…

I’m working on SDL audio drivers, and because the driver is in the linux
folder and then copied by the configure script to the src/audio
directory, the turn-around cycle for testing changes is extremely long.
Currently I run autogen.sh && make for each build. Is there any way to
improve the build-performance? Working in src/audio directly seems to
make a lot of trouble (but maybe I only got confused when working and
copying files all the time).

What about symlinks, would it be possible to create symlinks from the
src/audio filess to the src/audio/linux files to instead of copying
them? (at least on those platforms that support symlinks)

bye…

Hi…

I’m working on SDL audio drivers, and because the driver is in the linux
folder and then copied by the configure script to the src/audio
directory, the turn-around cycle for testing changes is extremely long.
Currently I run autogen.sh && make for each build. Is there any way to
improve the build-performance? Working in src/audio directly seems to
make a lot of trouble (but maybe I only got confused when working and
copying files all the time).

If you copy the file to src/audio, then just edit that, and type ‘make’,
the build process will be much shorter.

What about symlinks, would it be possible to create symlinks from the
src/audio filess to the src/audio/linux files to instead of copying
them? (at least on those platforms that support symlinks)

You’ll need to modify the top of acinclude.m4 and change the definition
of LINK_ARCH_SRC(). It used to use symbolic links, but the build process
failed using native mingw32.

I haven’t tested the native mingw32 configuration in a long time, so it
may be broken anyway, but I’d like to support it if possible.

-Sam Lantinga				(slouken at devolution.com)

Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec