In addition to the points that Joerg made ... autoconf is necessary even for software that runs only in Linux, because you have 32 bit versions, 64 bit versions, versions on other processors such as ARM and PowerPC. Even for the same O/S, sizes of objects differ, byte ordering differs, etc.
Seth Kurtzberg Hardware/Software Engineer On Sat, 16 Feb 2008 13:06:02 +0100 [EMAIL PROTECTED] (Joerg Schilling) wrote: > "Thomas Schmitt" <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > Joerg Schilling: > > > Why do you use autoconf if you write software that runs on Linux only? > > > > They produce the wellknown interface of > > ./configure ; make ; make install > ... > > > By principle, libburnia adapts to Linux, not vice versa. > > Sorry to see that you seem to be from a generation that does no longer know > the > rules from the late 1970s and early 1980s for creating OpenSource: > > Make sure that it runs on as many platforms as possible. > > Do not artificially prevent compilation on some platforms. > > Listen to people from other platforms to achieve better portability. > > Nonportable software undermines the OSS infrastructure. Just think of projects > like GNOME that claim wide portability but do not check the portability of all > libraries used. > > Jörg > > -- > EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin > [EMAIL PROTECTED] (uni) > [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ > URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- Seth Kurtzberg <[EMAIL PROTECTED]> Hardware and Software Engineer
