Mesa
Mesa is a 3-D graphics library which uses the OpenGL API (Application Programming Interface). Mesa cannot be called an implementation of OpenGL since the author did not obtain an OpenGL license from SGI. Furthermore, Mesa cannot claim OpenGL conformance since the conformance tests are only available to OpenGL licensees. Despite these technical/legal terms, you may find Mesa to be a valid alternative to OpenGL. Most applications written for OpenGL can use Mesa instead without changing the source code.
| Tags | Software Development Libraries |
|---|
Recent releases
- 28 May 2009 13:31
Changes: A segfault in DRI 1, a texture object memory leak, a state validation bug, some i965 GLSL bugs, and other minor bugs were fixed.
- 25 Apr 2009 20:55
Changes: Support for GLSL 1.20 was added. Intel DRI drivers now use GEM and DRI2. Many bugs were fixed. The "XMesa", "FXMesa", and "Allegro" interfaces were deprecated.
- 25 Sep 2008 17:50
Changes: The OpenGL 2.1 API is now implemented, though some drivers don't support it yet. Support for the Intel G41 chipset was added. Several bugs were fixed.
- 10 Apr 2008 13:43
Changes: A number of crashes and several other minor bugs were fixed.
- 14 Nov 2007 04:31
Changes: The build was enhanced with DESTDIR support, and building for MingW was fixed. Pkg-config files were added. Support for Intel G33/Q33/Q35 graphics chipsets was added. Several missing OpenGL 2.0 API entrypoints were added. Several display, crash, and memory leak problems were eliminated.
- All comments
Recent comments5.0.2
Looks like 5.0.2 wasn't tested too thoroughly. On RH7.2, libtool script dies with a syntax error, configure doesn't perform all Makefile.in substitutions properly, etc.
Re: circular RPM dependency problem solved
>
> % Don't use RPM, be a real man and
> compile
> % from source.
>
>
> Oh, yes; timecop bitching again.
He is right.
There are really rare cases where rpm packages
should depends on each other causing
a circular dependecy.
This is a packaging bug.
The best thing to do is to write your own rpm spec
file and compile it. 8)
Re: circular rpm dependencies problem
> Mesa-common-3.2.1-1rh61.i386.rpm
> requires Mesa-3.2.1-1rh61.i386.rpm to
> install... BUT
> Mesa-3.2.1-1rh61.i386.rpm requires
> requires
> Mesa-common-3.2.1-1rh61.i386.rpm to
> install.
>
> solution:
> rpm --install --nodeps
> Mesa-common-3.2.1-1rh61.i386.rpm
> rpm --install
> Mesa-3.2.1-1rh61.i386.rpm
>
>
the real solution:
rpm -Uvh Mesa-common-3.2.1-1rh61.i386.rpm Mesa-3.2.1-1rh61.i386.rpm
Re: circular RPM dependency problem solved
> Don't use RPM, be a real man and compile
> from source.
Oh, yes; timecop bitching again.
There's certainly a problem if common requires the base but since you will install them both, install them with the same command. This way all dependencies get filled.
Elementary... =)
circular RPM dependency problem solved
Don't use RPM, be a real man and compile from source.