Tuesday, February 28, 2012

Zenwalk-Minislack-Slackware :: Chrome from scratch

Links: libz and libxml2   file source w sloppy instructions   installation with decent library info
I followed the second instructions, linking the seven(7) libraries manually which Chrome utilzes. This avoids many update and fail issues.

initial failures

With everything properly in /opt, and libraries linked, a first run of Chrome brought only the following failures:
$ google-chrome
./google-chrome: /usr/lib/libz.so.1: no version information available (required by ./google-chrome)
./google-chrome: /usr/lib/libpng12.so.0: no version information available (required by ./google-chrome)
./google-chrome: /usr/lib/libnss3.so.1d: version `NSS_3.12.3' not found (required by ./google-chrome)

So libnss3, libpng, and libz. Updating libz apparently also requires a libxml2 update. Libnss is a mozilla security library and I believe the current version requires some other dependency updates. Libpng is probably straightforward. Not sure how many downstream dependencies these alter however.

Friday, February 17, 2012

ffmpeg to avconv

Links: libav.org - avconv, lavf   ffmpeg.org - ffmpeg still developed   xvid.org (xvidcore)   videlan.org (x264)   x264 settings
Edit: Ffmpeg (ffmgeg.org) was forked to avconv (libav.org). Both libav and ffmpeg both still use the libavcodec, but libav 0.8 appears to be the last to even be compatible with the previous ffmpeg. This post is to determine installation order for a robust avconv and describe any command changes from ffmpeg. So far (02/17/2012) order appears: 1) libav (includes libavcodec) 2) x264, 3) xvidcore

ffmpeg/avconv fork

Some confusion exists with the fork. Both ffmpeg and avconv use the same old ffmpeg logo seen here. Additionally, both are touting their use of libavcodec, so that it's unclear which project now has the most stable, fastest version of libavcodec. For now letting it go until I can get clarification on these issues.