On 08/12/2010 10:53 AM, tom fogal wrote:
> Can we go the other way? Put OSMesa symbols in libGL?
I gave this a successful try in the other thread. (Sorry for the
braiding of threads)
signature.asc
Description: OpenPGP digital signature
___
mesa-dev m
Dan Nicholson writes:
[snip]
> A possible compromise here would be to put glX* stubs in OSMesa, but
> _that_ seems perverse, too.
That would be wonderful for us, though ;)
Can we go the other way? Put OSMesa symbols in libGL?
That feels an iota less gross to me. Still, some day I'd like to pa
"Kevin H. Hobbs" writes:
> On 08/11/2010 05:18 PM, tom fogal wrote:
> > Right. This is exactly why Mesa's name mangling exists.
> > You mean you haven't been mangling this whole time? I guess I haven't
> > been reading these mails closely enough.
>
> It just seems perverse to have to use name ma
On 08/12/2010 07:52 AM, Dan Nicholson wrote:
On Thu, Aug 12, 2010 at 2:07 AM, Kevin H. Hobbs wrote:
On 08/11/2010 05:18 PM, tom fogal wrote:
Right. This is exactly why Mesa's name mangling exists.
You mean you haven't been mangling this whole time? I guess I haven't
been reading these mails c
On Thu, Aug 12, 2010 at 2:07 AM, Kevin H. Hobbs wrote:
> On 08/11/2010 05:18 PM, tom fogal wrote:
>> Right. This is exactly why Mesa's name mangling exists.
>> You mean you haven't been mangling this whole time? I guess I haven't
>> been reading these mails closely enough.
>>
>> -tom
>>
>
> It ju
On 08/11/2010 05:18 PM, tom fogal wrote:
> Right. This is exactly why Mesa's name mangling exists.
> You mean you haven't been mangling this whole time? I guess I haven't
> been reading these mails closely enough.
>
> -tom
>
It just seems perverse to have to use name mangling to deal with the
"Kevin H. Hobbs" writes:
> When I do :
>
> ./autogen.sh --with-driver=xlib --disable-gallium --enable-debug
>
> I get for example :
>
> $ nm lib/libGL.so | grep glDepthFunc
> 0020ce30 T glDepthFunc
> $ nm lib/libOSMesa.so | grep glDepthFunc
> 001ca760 T glDepthFunc
>
> As I und
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kevin H. Hobbs wrote:
> How is symbol visibility set up in mesa's shared objects?
>
> When I do :
>
> ./autogen.sh --with-driver=xlib --disable-gallium --enable-debug
>
> I get for example :
>
> $ nm lib/libGL.so | grep glDepthFunc
> 0020ce
How is symbol visibility set up in mesa's shared objects?
When I do :
./autogen.sh --with-driver=xlib --disable-gallium --enable-debug
I get for example :
$ nm lib/libGL.so | grep glDepthFunc
0020ce30 T glDepthFunc
$ nm lib/libOSMesa.so | grep glDepthFunc
001ca760 T glDepthFunc
