> But there are usually other calls than just calls of the SDL-lib. If
> one would only use SDL, then this is enough. But you cannot use any
> standard C-function or whatever, else you have also link against other
so.. what we need is s difinitive guide to producing SDL binary only
applications that should suit most modern linux distributions and not breach
any licencing issues.
I am at somepoint wanting to release some stuff as binary only for linux, my
mindset currently is just have a .deb for ubuntu/debian ( rashly assuming this
should mainly work across most version ( apart form libc issues raised earlier
perhaps) ) and perhaps a rpm build for the fedora types out there, anyone else
can go fish.
So.. to clarify for me ( dumbass who dosnt really pay attention ) ..
To build a 'universal' program for linux based systems, you would need static
links to libraies for, SDL family, and static links to a libc you use just to
be sure, and the theory is if you had all this the code /should/ run all by
it's merry self, apart from perhpas the sound issues raised earlier.
Would there be anyway to detect the sound system in use and have your
binary / a
script adapt to suit?
IMHO this is the kinda nonsence that helps hold linux back from your average
users.. i dont dare to count the hours i have spent in dependancy hell ;) but
it is a long time invloving alot of cigarettes.
so i econ the best way to distribute linux binaries is to do some slogging and
build a set of binaires for all the major distributions/*nix types
use about the place... but then i suspect alot of people arnt really
going to be
interested unless it is in thier distributions repositories anyway, i
know a few
who will only install software via reps becasue of fear of exploding thier
SDL mailing list