Menu
▾
▴
mesa3d-dev
|
From: Olivier M. <Oli...@cy...> - 2000-11-27 09:33:15
|
Sven Goethel wrote: > Thanxs a lot ! > > How about integrating the SGI GLU Sources to the Mesa distribution ? > Did you asked Brian ? Yes. Brian told me that he would like to see this SGI GLU integrated into Mesa in a forthcoming version of Mesa, but I cannot tell you when. There may be problems with mixing different licenses into a single package... (SGI OSS license is different from Mesa LGPL, don't ask me where!). > The current GLU 1.1 Version is very useless > - - as Brian stated also on his Mesa site ! > > Yours, Sven > - -- > mailto:sgo...@ja... -Olivier |
|
From: Brian P. <br...@va...> - 2000-11-27 16:38:49
|
Olivier Michel wrote: > > Sven Goethel wrote: > > > Thanxs a lot ! > > > > How about integrating the SGI GLU Sources to the Mesa distribution ? > > Did you asked Brian ? > > Yes. Brian told me that he would like to see this SGI GLU integrated > into Mesa in a forthcoming version of Mesa, but I cannot tell you when. I haven't started that work either, yet. > There may be problems with mixing different licenses into a single > package... (SGI OSS license is different from Mesa LGPL, don't ask me > where!). The main Mesa library is not LGPL, it's copyrighted XFree86-style. There are some other components in the Mesa distro such as GLUT, GLU and some drivers which have other copyrights. It's explained in the docs. The SI GLU copyright is compatible with XFree86 so there should be no problem including the sources with Mesa. The concern I have is what to do for people who do not have a C++ compiler. If they can't compile the SI GLU they'll either need to use the old Mesa GLU or find a precompiled library for their system. And until they solve that, they can't run many of the Mesa demos, etc. -Brian |
|
From: Sven G. <sgo...@ja...> - 2000-11-27 22:41:39
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 27 November 2000 17:44, Brian Paul wrote: > Olivier Michel wrote: > > Sven Goethel wrote: > > > Thanxs a lot ! > > > > > > How about integrating the SGI GLU Sources to the Mesa distribution ? > > > Did you asked Brian ? > > > > Yes. Brian told me that he would like to see this SGI GLU integrated > > into Mesa in a forthcoming version of Mesa, but I cannot tell you when. > > I haven't started that work either, yet. > > > There may be problems with mixing different licenses into a single > > package... (SGI OSS license is different from Mesa LGPL, don't ask me > > where!). > > The main Mesa library is not LGPL, it's copyrighted XFree86-style. > There are some other components in the Mesa distro such as GLUT, GLU > and some drivers which have other copyrights. It's explained in > the docs. > > The SI GLU copyright is compatible with XFree86 so there should be > no problem including the sources with Mesa. The concern I have is > what to do for people who do not have a C++ compiler. If they > can't compile the SI GLU they'll either need to use the old Mesa > GLU or find a precompiled library for their system. And until > they solve that, they can't run many of the Mesa demos, etc. > > -Brian Aehem, well, but how about splitting the Mesa distribution from: MesaLib & MesaDemos to: MesaLib & (MesaSGIGLU || MesaGLU) & MesaDemos where, of course, the MesaSGIGLU is preferred .. just an idea. another Q: why do you revert the MesaGLU to GLU 1.1 ? kind regards, sven - -- mailto:sgo...@ja... www : http://www.jausoft.com ; pgp: http://www.jausoft.com/gpg/ voice : +49-521-2399440, +49-170-2115963; fax: +49-521-2399442 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6IuL4HdOA30NoFAARAtQ1AJ4oLroYFigJWYLOplMXk2dQaejbLQCgj9C1 kdzzSQDAx4+AdF7onEIFcIA= =Yju6 -----END PGP SIGNATURE----- |
|
From: Brian P. <br...@va...> - 2000-11-27 22:49:12
|
Sven Goethel wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Monday 27 November 2000 17:44, Brian Paul wrote: > > Olivier Michel wrote: > > > Sven Goethel wrote: > > > > Thanxs a lot ! > > > > > > > > How about integrating the SGI GLU Sources to the Mesa distribution ? > > > > Did you asked Brian ? > > > > > > Yes. Brian told me that he would like to see this SGI GLU integrated > > > into Mesa in a forthcoming version of Mesa, but I cannot tell you when. > > > > I haven't started that work either, yet. > > > > > There may be problems with mixing different licenses into a single > > > package... (SGI OSS license is different from Mesa LGPL, don't ask me > > > where!). > > > > The main Mesa library is not LGPL, it's copyrighted XFree86-style. > > There are some other components in the Mesa distro such as GLUT, GLU > > and some drivers which have other copyrights. It's explained in > > the docs. > > > > The SI GLU copyright is compatible with XFree86 so there should be > > no problem including the sources with Mesa. The concern I have is > > what to do for people who do not have a C++ compiler. If they > > can't compile the SI GLU they'll either need to use the old Mesa > > GLU or find a precompiled library for their system. And until > > they solve that, they can't run many of the Mesa demos, etc. > > > > -Brian > > Aehem, well, but how about splitting the Mesa distribution from: > MesaLib & MesaDemos > to: > MesaLib & (MesaSGIGLU || MesaGLU) & MesaDemos > > where, of course, the MesaSGIGLU is preferred .. Yes, I might do that. > another Q: why do you revert the MesaGLU to GLU 1.1 ? Because there were a few severe bugs in the (unfinished) 1.2 tessellator implementation. -Brian |
|
From: Stephen J B. <sj...@li...> - 2000-11-28 13:43:51
|
On Mon, 27 Nov 2000, Sven Goethel wrote: > Aehem, well, but how about splitting the Mesa distribution from: > MesaLib & MesaDemos > to: > MesaLib & (MesaSGIGLU || MesaGLU) & MesaDemos > > where, of course, the MesaSGIGLU is preferred .. If there are going to be ugly issues with which C++ runtime library SGI-GLU pulls-in/requires then I think it's vital from an application support perspective to minimise the number of varients there can be out there. I would not want to see (say) Debian and RedHat shipping the SGI version of GLU with SuSE and Corel shipping GLU-classic. I'd also oppose splitting GLU off from Mesa's main download because that will result in lots of end-users installing "Mesa" and yet having no valid GLU implementation because they failed to download/install it. Supporting OpenGL applications under Linux is hard enough as it is - look at the mail archives for an active OpenGL application (TuxRacer for example) and you'll see that at least 95% of the posts are OpenGL installation problems of one kind or another. That consumes an insane amount of people's time - PLEASE, let's not make it any harder. IMHO, 99% of widely distributed OpenGL apps for Linux will not be using the problematic functions in GLU-classic - because those programs were almost certainly developed using that library and either don't use the broken functions or have work-arounds that work OK. Hence most existing applications will get no benefit from SGI-GLU. In any case, the kinds of applications that need things like tesselators and spline patches tend not to be games - more often they are things like scientific visualisers and custom applications which are not widely circulated. Hence, I suggest that until the g++ standard library stuff settles A down, we avoid making SGI-GLU the default. I think the Mesa documentation should point out that we *WILL* make the transition - but not yet - and advise people who experience problems with GLU-classic to switch over immediately. Meanwhile I think we should continue to ship GLU-classic by default. --- Steve Baker (817)619-2657 (Vox/Vox-Mail) L3Com/Link Simulation & Training (817)619-2466 (Fax) Work: sj...@li... http://www.link.com Home: sjb...@ai... http://web2.airmail.net/sjbaker1 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X