Surely it'd be less difficult nowadays, with the job market in its current
state?
Rob
On Tue, 15 Jul 2003, Alex Deucher wrote:
This proposal comes up periodically on this and other xfree lists, but
never really goes anywhere. Why not raise money from the open source
community to fund
On Tue, 15 Jul 2003, Mark Vojkovich wrote:
It is very difficult to convert money into code. It's probably
easier to raise the money than it is to find a way to convert
that into code.
Not exactly a driver, but I was under the impression that remote GLX
support (ie hardware accelerated 3D
Where can I find good tutorials for development with xlib.
___
Yahoo! Mail
Mais espaço, mais segurança e gratuito: caixa postal de 6MB, antivírus, proteção
contra spam.
http://br.mail.yahoo.com/
What about tungsten graphics or Providenza Boekelheide, Inc. (Tim
Robert's company? Plus I'm sure there are other small development
companies that would be interested.
Alex
--- Mark Vojkovich [EMAIL PROTECTED] wrote:
On Tue, 15 Jul 2003, Alex Deucher wrote:
This proposal comes up
Support for HW accelerated indirect rendering is just a matter of
restructuring some library interfaces so that GLX commands can get
decoded and sent to the hardware rather than the sw renderer. It's in
the pipeline for future development by the DRI folks, but if it were
sponsored, it might
On Mer, 2003-07-16 at 15:08, Alex Deucher wrote:
Support for HW accelerated indirect rendering is just a matter of
restructuring some library interfaces so that GLX commands can get
decoded and sent to the hardware rather than the sw renderer. It's in
the pipeline for future development by
On Wed, Jul 16, 2003 at 04:36:33PM +0100, Alan Cox wrote:
On Mer, 2003-07-16 at 15:08, Alex Deucher wrote:
Support for HW accelerated indirect rendering is just a matter of
restructuring some library interfaces so that GLX commands can get
decoded and sent to the hardware rather than the sw
We have a bug report at
http://bugs.xfree86.org/show_bug.cgi?id=503
that suggests that when building libraries with callbacks using gcc
the option -fexeptions should be used. It enables C++ programs
to catch the exceptions.
I've talked to a gcc expert and he says that using this option is
sane.
On Wed, 2003-07-16 at 13:11, Egbert Eich wrote:
We have a bug report at
http://bugs.xfree86.org/show_bug.cgi?id=503
that suggests that when building libraries with callbacks using gcc
the option -fexeptions should be used. It enables C++ programs
to catch the exceptions.
I've talked to
