Re: tarball should include m4-files needed for autoconf
Bernhard Praschinger <[email protected]>
| Newsgroups | gmane.comp.video.mjpeg.devel |
|---|---|
| Message-ID | <[email protected]> |
Hallo >> But the SDL development package is not that widely installed. By far the most > The two ways around that which I have used are: 1) check the "add > matching devel packages" when installing the system (I know SuSE offers > this option) or 2) 'cvs checkout' and build it (which is what I do for > OSX - painless build). > >> multimedia packages nowadays don't use SDL (for a reason). > At one time it was widely used - and I've never had any problems with > it. Can you tell us (or at least me) a more common way nowdays used ? I know about on other problem latent problem. We also have a problem that we use oss for recording and not alsa directly. >> This is usual practice, also for other projects. Users (the ones who call >> configure; make) need only mandatory requirements, developers (the ones who >> call ./autogen.sh) need much more (like libtool, automake, autoconf plus >> all m4 files)... What worries me a bit in the text is the thing that: You must then call aclocal with aclocal -I m4 options to search in that directory before the system library. I do not know how the *.m4 files changes when you use different version of SDL. And I have a little fear that we might also cause problems when we add the m4 file from a older/newer version of SDL. auf hoffentlich bald, Berni the Chaos of Woodquarter Email: [email protected] www: http://www.lysator.liu.se/~gz/bernhard ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV