* [Bug 45473] New: vdpau-r300 requires softpipe
@ 2012-02-01 1:36 bugzilla-daemon
2013-01-11 9:45 ` [Bug 45473] " bugzilla-daemon
0 siblings, 1 reply; 2+ messages in thread
From: bugzilla-daemon @ 2012-02-01 1:36 UTC (permalink / raw)
To: dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=45473
Bug #: 45473
Summary: vdpau-r300 requires softpipe
Classification: Unclassified
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: neotheuser@ymail.com
When compiling vdpau-r300 (libvdpau_r300.so) I get a compiling error:
No rule to make target
`../../../../src/gallium/drivers/softpipe/libsoftpipe.a', needed by
`../../../../lib/gallium/libvdpau_r300.so'. Stop.
The solution:
Instead of ./autogen.sh --with-dri-drivers="" --with-gallium-drivers=r300
--enable-vdpau
add swrast to gallium driver
./autogen.sh --with-dri-drivers="" --with-gallium-drivers=r300,swrast
--enable-vdpau
Compiles fine now and without error.
Should gallium targets for real hardware use softpipe code / is it necessary?
If so, maybe move the necessary code from softpipe into a common directory
which other gallium targets can easily find, without having to build a whole
new gallium driver such as softpipe to satisfy dependencies.
Reported by Alec Ari <neotheuser@ymail.com>
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-01-11 9:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-02-01 1:36 [Bug 45473] New: vdpau-r300 requires softpipe bugzilla-daemon
2013-01-11 9:45 ` [Bug 45473] " bugzilla-daemon
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).