Changeset 9731 to configure prevents ability to build for xvmc_vld

[goldwein@…]

Can no longer enable-xvmc-vld using configure

[anonymous]

no it doesn't, the logic is now:-

if you have XVMCW use that, else if you have NVIDIAXVMC installed use that, else check for viaXvMCPro, viaXvMC, i810XvMC in that order.

so there is only a problem if you have installed the NVidia video drivers but for some reason want to use via xvmc instead.

[goldwein@…]

Thanks. Here is the use case:

User wishes to compile frontend for a VIA EPIA M1000 diskless system that utilizes viaXvMC. User will compile the frontend on an NVidia machine.

JG

[danielk]

The user should run ./configure on the epia machine.

[Colin Guthrie <mythtv@…>]

For what it's worth, I would do this. I compile myth to run on my EPIA but do so on a much faster machine.... Fortunately my nVidia machine is an x86_64 so I compile on my "server/backend" which is ATi, but I for one would be tripped up by this autoselect. Perhaps it could be overridden by an additional option?

[anonymous]

selectable xvmclib

[goldwein@…]

How does one "run ./configure on the epia machine" if the epia machine is a diskless frontend?

[anonymous]

goldwein, mount? although if you're cunning and careful enough to be doing builds on different hardware surely you're capable of coming up with a workaround and/or patch?

Anyhow, patch to allow specific xvmc library selection attached to ticket.

[danielk]

(In [9751]) Closes #1706. Adds a xvmc-lib option to allow you to override the detected XvMC library.