[ATrpms-devel] libXvMCW (and -devel for newer distros)
Axel Thimm
Axel.Thimm at ATrpms.net
Wed May 17 22:49:50 CEST 2006
On Wed, May 17, 2006 at 12:24:43PM -0700, Chris Petersen wrote:
> > Newer distros, or say better, FC5 gets its XvMCW from the vendor
> > itself :)
>
> I figured that was why you were building it with no files, however, my
> fc5 systems have no /etc/X11/XvMCConfig file, and I find no references
> for XvMCW in any yum searches.
>
> > I'm not sure whether I will be able to really get rid of this dummy
> > package as it is needed for keeping specfiles for FC5 and pre-FC5/RHEL
> > the same. In that case it would have to be better documented in
> > Summary and %description.
>
> That was why I suggested switching to a file-based requirement instead
> of package-based. But like I said, that necessary file doesn't seem to
> appear in FC5's XvMC packages. At least, I *thought* that the file was
> necessary. Maybe it should just be a requirement for
> %{_libdir}/libXvMCW.so.1 ? I know that fedora is really pushing for
> people to set their requirements up as file-based rather than
> package-based to solve stuff like this.
>
> Looks like I was wrong and mythtv compiles just fine without the
> /etc/X11/XvMCConfig file. But in this process, I ran into another issue
> (in svn, not sure about .19). XvMCW is *not* required for mythtv. In
> fact, it actually hinders performance of the new opengl menu code, which
> can be pushed to nvidia's xvmc handler but not the VLD stuff.
>
> Do you build your packages primarily with xvmcw instead of the
> vendor-specific libraries? I think that as mythtv adds more
> vendor-specific options, it might be wise for me to add support to the
> configure script to have something like "prefer-xvmcw" because currently
> xvmcw doesn't give you access to the nice opengl stuff.
The main idea was to have one binary to serve both nvidia, intel and
via users, and xvmcw was the only way to do do. If there are better
ways I'm all for it :)
--
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20060517/983c9f4f/attachment.bin
More information about the atrpms-devel
mailing list