SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm on xfce at the moment. I tried to find a good burner for xfce and I found xfburn. After a few hours of trying to make it work, I gave up. I failed to get it to read and burn audio files(.wav and .mp3) and it froze a lot on me. Killing the process id didn't work either and I had to restart the computer to get rid of it. And also most importantly, I couldn't get it do multisession data writing.
I finally came across X-CD-Roast and it got the job done. As far as I know, X-CD-Roast uses cdrtools such as cdrecord. It can write data, audio, capable of doing multisession recordings, and all other great stuff.
Oh yea and I forgot to mention...that's a really cool guide you have there. I know nothing about kde or k3b. I heard from rumors that you can use k3b on xfce 4.4.*. I haven't tried it yet, but when I do I'll be sure to check back at your guide. I'm bookmarking your page if you don't mind, hehe.
Would be even better if all the references you make to the different software requirements were active hyperlinks.
I thought about that but wanted to keep the guide generic. Still, most people trying to build Slackware into a multimedia machine are likely to be new people rather than veteran Slackers. Links to the build scripts and complete packages might be a good idea, but the challenge there is the links change every Slackware release. Perhaps I'll add links to slackbuilds.org and slacky.eu. People who want complete packages can try the latter.
Quote:
I'm on xfce at the moment. I tried to find a good burner for xfce and I found xfburn . . . I finally came across X-CD-Roast and it got the job done.
The Zenwalk folks use Brasero. I don't know if that is a good selection, but Zenwalk is an Xfce-only Slackware derivative distro.
Nice guide. Just a few minor things with the digiKam part. imlib2 has not been a dependency of kipi-plugins for some time now and dcraw is not a dependency of digiKam or kipi-plugins, since libkdcraw includes its own version of dcraw. Also, sqlite is now included with digiKam itself. I would make reference somewhere that if users wish to compile against the sqlite included with Slackware 12.2, that they will need to add '--without-included-sqlite3' to their configure. The digiKam slackbuild at SBo uses this option by default.
rc nai:
xfburn just came out with version 0.4.0. They may have fixed the issues you have been having with it. Might be worth another look.
Just a few minor things with the digiKam part. imlib2 has not been a dependency of kipi-plugins for some time now and dcraw is not a dependency of digiKam or kipi-plugins, since libkdcraw includes its own version of dcraw. Also, sqlite is now included with digiKam itself. I would make reference somewhere that if users wish to compile against the sqlite included with Slackware 12.2, that they will need to add '--without-included-sqlite3' to their configure. The digiKam slackbuild at SBo uses this option by default.
I want to thank everybody for your feedback. I hope the short guide helps others. Perhaps some day I'll add direct links to the build scripts or packages, but for now I think a decent foundation exists.
I never thought I'd see multimedia "just working right" on Slackware. It took an evening for me to find and install the "Basic Support" packages. The transcode SlackBuild for 12.2 didn't compile properly, so I used a version for 12.1 and it seems to work okay. Great writeup!
Hmm. I just updated transcode the other day in my 12.2 box and the package built without errors. On the other hand, I haven't built the multimedia support from scratch in a long time. Perhaps that would be a good way to test my guide.
Woodsman, if it helps, this is part of the console output from the 12.2 slackbuild for transcode-1.0.7. The install was on a near virgin Slack 12.2.
And to answer the obvious question, I did install 12.2 packages in the recommended order (binary packages from slacky.eu when available, otherwise built from packages at slackbuilds.org. I threw in a couple of ldconfigs for good measure.
Code:
checking for pkgconfig support for libavcodec... yes
checking how to determine LIBAVCODEC_CFLAGS... pkg-config
checking libavcodec/avcodec.h usability... yes
checking libavcodec/avcodec.h presence... yes
checking for libavcodec/avcodec.h... yes
checking how to determine LIBAVCODEC_LIBS... pkg-config
checking for avcodec_thread_init in -lavcodec... no
----------------------------------------
Summary for transcode 1.0.7:
----------------------------------------
core options
----------------------------------------
static AV-frame buffering yes
network (sockets) streams yes
NUV format support yes
experimental xio no
Default xvid export xvid4
A52 default decoder yes
libavcodec
----------------------------------------
headers -I/usr/local/include
libraries
build
version
statically linked
hardware support
----------------------------------------
v4l/v4l2 yes
OSS no
bktr no
sunau no
optional package support
----------------------------------------
IBP no
X11 yes
libmpeg2 yes
libpostproc no
freetype2 yes
avifile no
lame yes
ogg yes
vorbis yes
theora yes
libdvdread yes
pvm3 no
libdv yes
libquicktime yes
lzo yes
a52 yes
libmpeg3 no
libxml2 yes
mjpegtools no
sdl yes
libfame no
imagemagick no
libjpeg yes
bsdav no
iconv yes
ERROR: requirement failed: cannot link against libavcodec
libavcodec can be found in the following packages:
libavcodec http://www.ffmpeg.org/
ERROR: option '--enable-libpostproc' failed: cannot compile libpostproc/postpro
libpostproc/postprocess.h can be found in the following packages:
libpostproc http://www.ffmpeg.org/
ERROR: option '--enable-libpostproc' failed: cannot link against libpostproc
libpostproc can be found in the following packages:
libpostproc http://www.ffmpeg.org/
Please see the INSTALL file in the top directory of the
transcode sources for more information about building
transcode with this configure script.
Edit to Add: I forgot that after the transcode slackbuild failed, I'd rebuilt ffmpeg from a recent subversion snapshot and left it installed that way. So to confirm my complaint, I uninstalled that version, reinstalled the package ffmpeg-20081214-i686-1sl.tgz and tried again. The outcome was essentially the same. (Sorry for the complication, that's what happens when you're installing stuff manually.)
Last edited by DavidHindman; 12-29-2008 at 03:59 PM.
Reason: Add more information
All of the referenced files are part of ffmpeg. I am not software guru with respect to understanding the nuances of software, but I would consider rebuilding and reinstalling ffmpeg. I used the build script from www.slackbuilds.org.
Note: there is a small bug with building ffmpeg. The bug is being remedied in the slackbuild script but is not yet uploaded. The ffmpeg configure file is hard-coded to look for a TEMPDIR variable. If you use /tmp as your temporary working directory then run the build script like this: TEMPDIR=/tmp sh ffmpeg.SlackBuild.
All of the referenced files are part of ffmpeg. I am not software guru with respect to understanding the nuances of software, but I would consider rebuilding and reinstalling ffmpeg. I used the build script from www.slackbuilds.org.
Note: there is a small bug with building ffmpeg. The bug is being remedied in the slackbuild script but is not yet uploaded. The ffmpeg configure file is hard-coded to look for a TEMPDIR variable. If you use /tmp as your temporary working directory then run the build script like this: TEMPDIR=/tmp sh ffmpeg.SlackBuild.
Of course, then try again to build transcode.
I slackbuilt ffmpeg with that workaround and reinstalled it. The transcode slackbuild then completed without error.
What's clear to me now is that the packages called out in the writeup all need to be built with compatible options. Mixing multimedia packages from different sources runs the risk of incompatible build options. If I did it all over again, I'd just get all the packages from slackbuilds.org and not try to mix in packages from other sources.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
