Keith Whitwell wrote:
> Brian Paul wrote:
>
>>Ian Romanick wrote:
>>
>>>-BEGIN PGP SIGNED MESSAGE-
>>>Hash: SHA1
>>>
>>>It looks like adding support for GLX_SGI_make_current_read is almost as
>>>easy as just enabling the extension thanks to Mesa's internal
>>>framebuffer object changes. T
Brian Paul wrote:
> Ian Romanick wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> It looks like adding support for GLX_SGI_make_current_read is almost as
>> easy as just enabling the extension thanks to Mesa's internal
>> framebuffer object changes. Thanks Brian!
>>
>> However, the
Ian Romanick wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> It looks like adding support for GLX_SGI_make_current_read is almost as
> easy as just enabling the extension thanks to Mesa's internal
> framebuffer object changes. Thanks Brian!
>
> However, there is one thing that I don
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It looks like adding support for GLX_SGI_make_current_read is almost as
easy as just enabling the extension thanks to Mesa's internal
framebuffer object changes. Thanks Brian!
However, there is one thing that I don't get. Each driver supplies a
GetB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ulrich von Zadow wrote:
> as of Version 6.5.1, glXWaitVideoSyncSGI is no longer exported by Mesa.
> Is this intentional?
Yes. Use glXGetProcAddressARB.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFL7B2X1gOwKyEAw8RAt3GAJ91
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jin, Gordon wrote:
> Ian Romanick wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Jin, Gordon wrote:
>>
>>> I see following error message when building mesa tip. This seems to
>>> be regression in recent 1-2 days.
>> Which target are y
On 13/10/06, Ian Romanick <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Micha? Król wrote:
> > I cannot successfully link current cvs mesa on Visual C++ 6.0. The
> > error log follows.
>
> All of those symbols should come from src/mesa/main/dispatch.c. After
> ha
Hi,
as of Version 6.5.1, glXWaitVideoSyncSGI is no longer exported by Mesa.
Is this intentional?
Regards,
Uli
--
Ulrich von Zadow | Software Development Unit Head
ART+COM AG
Kleiststr. 23-26 | 10787 Berlin | Germany
phone: +49.30.21001-464
fax: +49.30.21001-555
[EMAIL PROTECTED]
http:/
Ian Romanick wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jin, Gordon wrote:
>
>> I see following error message when building mesa tip. This seems to
>> be regression in recent 1-2 days.
>
> Which target are you building?
Linux on Intel 915G system.
-Gordon
---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Micha? Król wrote:
> I cannot successfully link current cvs mesa on Visual C++ 6.0. The
> error log follows.
All of those symbols should come from src/mesa/main/dispatch.c. After
having this come up again and again, it's pretty obvious the VC++ has
s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jin, Gordon wrote:
> I see following error message when building mesa tip. This seems to be
> regression in recent 1-2 days.
Which target are you building?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFL5kWX1gOwKyEAw8RAuOvA
Michal Krol wrote:
> I cannot successfully link current cvs mesa on Visual C++ 6.0. The
> error log follows.
>
> Configuration: gdi - Win32 Debug x86
> Compiling...
> driverfuncs.c
> wgl.c
> wmesa.c
> Generating Code...
> Linking...
>Creating library Deb
Jin, Gordon wrote:
> Hi all,
>
> I see following error message when building mesa tip. This seems to be
> regression in recent 1-2 days.
>
> indirect.c: In function ‘__indirect_glGetPolygonStipple’:
> indirect.c:4212: warning: unused variable ‘state’
> indirect.c: In function ‘glAreTexturesResid
I cannot successfully link current cvs mesa on Visual C++ 6.0. The
error log follows.
Configuration: gdi - Win32 Debug x86
Compiling...
driverfuncs.c
wgl.c
wmesa.c
Generating Code...
Linking...
Creating library Debug_x86/OPENGL32.lib and object Debug_x86/
14 matches
Mail list logo