Greetings,
I'm currently trying to migrate an old in-house app (which no longer
have the source for) to a new Linux box. Previously this app ran on a
RH6.2 box, and I've noticed some strange behaviour in how this app
uses Mesa, specifically the glXUseXFont() function. I was seeing some
som
On Tue, May 13, 2008 at 5:04 AM, George - <[EMAIL PROTECTED]> wrote:
>
> > Date: Mon, 12 May 2008 12:25:26 -0400
> > From: [EMAIL PROTECTED]
> > To: [EMAIL PROTECTED]
> > Subject: Re: [Mesa3d-dev] drixorg: software renderer with dri_interface.h
> > CC: mesa3d-dev@lists.sourceforge.net
>
> >
> > Wow
If you look at the nightly VTK dashboard results for these two builds...:
http://www.cdash.org/CDash/viewTest.php?onlyfailed&buildid=74530
http://www.cdash.org/CDash/viewTest.php?onlyfailed&buildid=74372
...and you click on any of the FAILED links (like this one:
http://www.cdash.org/CDash/testDet
On Tue, May 13, 2008 at 5:21 AM, Keith Whitwell
<[EMAIL PROTECTED]> wrote:
>
> George,
>
> How about a slight tweak to Kristian's request -- would it be possible to
> use "swrast" instead of just "sw"?
>
> This is the mesa swrast module packaged into a dri driver structure, and
> maintaining that n
George,
How about a slight tweak to Kristian's request -- would it be possible to use
"swrast" instead of just "sw"?
This is the mesa swrast module packaged into a dri driver structure, and
maintaining that name helps keep this clear. I guess also using swrast
differentiates this slightly f
> Date: Mon, 12 May 2008 12:25:26 -0400
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: [Mesa3d-dev] drixorg: software renderer with dri_interface.h
> CC: mesa3d-dev@lists.sourceforge.net
>
> Wow, that's awesome work. My initial plan was to just wrap a dri
> interface around the