On 9/7/12 11:09 PM, Matt Turner wrote:
On Fri, Sep 7, 2012 at 1:49 PM, Thomas Hellström <[email protected]> wrote:
On 9/7/12 10:39 PM, Matt Turner wrote:
I'm converting the remaining static Makefile to automake, so xa and
xa-vmwgfx is on my todo list.

I'm very confused by the build though. It seems that the xa state
tracker is built and linked into a single .o file, which is then
statically linked into xa-vmwgfx. This is reasonably sensible, but
then we also build a libxatracker.so file which is installed to the
system that nothing links to.

Can I switch this to xa-vmwgfx linking to a shared libxatracker.so? Or
perhaps just linking it statically and not installing a libxatracker
file at all. Either of these seem more like the right thing to do, but
not being familiar with this code I thought it better to ask.

Thanks,
Matt
The xa-vmwgfx target actually builds libxatracker.so, which is a library
used
by external applications, like libGL.so, but currently it works only with
vmware.

/Thomas

Ahh, I see. I had thought (probably because I was expecting the
result) that xa-vmwgfx built a DDX called *_drv.so.
OK. Yes that was the old xorg-vmwgfx target which is now removed.
Instead the "external application" I was referring to is the vmware DDX, which is built as a freestanding module, and it uses libxatracker.so for acceleration
if present.

/Thomas


Thanks for your quick response!
Matt

_______________________________________________
mesa-dev mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Reply via email to