mesa3d-users

Re: [Mesa3d-users] Mesa 7.3 release candidate 1

[Littlebob <lit...@gm...>]

The commit, "glsl: move declaration before code" fixed the the error
that I was getting.

Thanks!

On Wed, Jan 14, 2009 at 3:23 PM, Brian Paul <br...@vm...> wrote:
>
> Yes, there's a new VC8 project file.  I removed the stray swizzle.c from it.  I'll try to make 7.3-rc2 tarballs/zips tonight.
>
> -Brian
>
> Karl Schultz wrote:
>>
>> Brian,
>>
>> Did anyone submit a new project file for Visual Studio?  If not, I can
>> make one later this evening using the latest RC build.  Let me know.
>>
>> Karl
>>
>>
>> On Wed, Jan 14, 2009 at 12:08 PM, Brian Paul <br...@vm...> wrote:
>>>
>>> Littlebob wrote:
>>>>
>>>> I'm getting several errors while trying to compile the latest source of
>>>> mesa from the GIT repository in MS visual c++ 2005. As I seem to always
>>>> have problems while others do not, it is probably something that I'm
>>>> doing wrong.
>>>
>>> Try removing swizzle.c from your project file.  It shouldn't be there.
>>>
>>> Don't know about the other errors.
>>>
>>> -Brian
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by:
>>> SourcForge Community
>>> SourceForge wants to tell your story.
>>> http://p.sf.net/sfu/sf-spreadtheword
>>> _______________________________________________
>>> Mesa3d-users mailing list
>>> Mes...@li...
>>> https://lists.sourceforge.net/lists/listinfo/mesa3d-users
>>>
>> .
>>
>

[Mesa3d-users] [PATCH] Use variable library name in pkg-config output.

[tom f. <tf...@al...>]

Previously the pkg-config output files would contain `-lGL' and
`-lGLU', even if the user modified their configuration to build
libraries with different names.  This modifies the pkg-config
inputs, and corresponding makery, so that modifying the output
library name will cause the appropriate updated name to appear in
the pkg-config `-l' option.
---
 src/glu/Makefile  |    3 ++-
 src/glu/glu.pc.in |    2 +-
 src/mesa/Makefile |    3 ++-
 src/mesa/gl.pc.in |    2 +-
 4 files changed, 6 insertions(+), 4 deletions(-)

diff --git a/src/glu/Makefile b/src/glu/Makefile
index e519dfe..5c26ead 100644
--- a/src/glu/Makefile
+++ b/src/glu/Makefile
@@ -22,7 +22,8 @@ pcedit = sed \
 	-e 's,@GLU_PC_REQ@,$(GLU_PC_REQ),' \
 	-e 's,@GLU_PC_REQ_PRIV@,$(GLU_PC_REQ_PRIV),' \
 	-e 's,@GLU_PC_LIB_PRIV@,$(GLU_PC_LIB_PRIV),' \
-	-e 's,@GLU_PC_CFLAGS@,$(GLU_PC_CFLAGS),'
+	-e 's,@GLU_PC_CFLAGS@,$(GLU_PC_CFLAGS),' \
+	-e 's,@GLU_LIB@,$(GLU_LIB),'
 glu.pc: glu.pc.in
 	$(pcedit) $< > $@
 
diff --git a/src/glu/glu.pc.in b/src/glu/glu.pc.in
index bc2517e..f7d9109 100644
--- a/src/glu/glu.pc.in
+++ b/src/glu/glu.pc.in
@@ -8,6 +8,6 @@ Description: Mesa OpenGL Utility library
 Requires: @GLU_PC_REQ@
 Requires.private: @GLU_PC_REQ_PRIV@
 Version: @VERSION@
-Libs: -L${libdir} -lGLU
+Libs: -L${libdir} -l@GLU_LIB@
 Libs.private: @GLU_PC_LIB_PRIV@
 Cflags: -I${includedir} @GLU_PC_CFLAGS@
diff --git a/src/mesa/Makefile b/src/mesa/Makefile
index 6b40570..8f8259e 100644
--- a/src/mesa/Makefile
+++ b/src/mesa/Makefile
@@ -95,7 +95,8 @@ gl_pcedit = sed \
 	-e 's,@VERSION@,$(MESA_MAJOR).$(MESA_MINOR).$(MESA_TINY),' \
 	-e 's,@GL_PC_REQ_PRIV@,$(GL_PC_REQ_PRIV),' \
 	-e 's,@GL_PC_LIB_PRIV@,$(GL_PC_LIB_PRIV),' \
-	-e 's,@GL_PC_CFLAGS@,$(GL_PC_CFLAGS),'
+	-e 's,@GL_PC_CFLAGS@,$(GL_PC_CFLAGS),' \
+	-e 's,@GL_LIB@,$(GL_LIB),'
 
 gl.pc: gl.pc.in
 	$(gl_pcedit) $< > $@
diff --git a/src/mesa/gl.pc.in b/src/mesa/gl.pc.in
index 0462b9f..97b8659 100644
--- a/src/mesa/gl.pc.in
+++ b/src/mesa/gl.pc.in
@@ -7,6 +7,6 @@ Name: gl
 Description: Mesa OpenGL library
 Requires.private: @GL_PC_REQ_PRIV@
 Version: @VERSION@
-Libs: -L${libdir} -lGL
+Libs: -L${libdir} -l@GL_LIB@
 Libs.private: @GL_PC_LIB_PRIV@
 Cflags: -I${includedir} @GL_PC_CFLAGS@
-- 
1.6.0.4

[Mesa3d-users] Mesa 7.3 release candidate 2

[Brian P. <br...@vm...>]

The second 7.3 release candidate can be downloaded from 
http://www.mesa3d.org/beta/

Since rc1 there's been build fixes for OpenBSD and Windows, plus an 
assortment of bug fixes.

-Brian

Re: [Mesa3d-users] Mesa 7.3 release candidate 1

[Brian P. <br...@vm...>]

Yes, there's a new VC8 project file.  I removed the stray swizzle.c from 
it.  I'll try to make 7.3-rc2 tarballs/zips tonight.

-Brian

Karl Schultz wrote:
> Brian,
> 
> Did anyone submit a new project file for Visual Studio?  If not, I can
> make one later this evening using the latest RC build.  Let me know.
> 
> Karl
> 
> 
> On Wed, Jan 14, 2009 at 12:08 PM, Brian Paul <br...@vm...> wrote:
>> Littlebob wrote:
>>> I'm getting several errors while trying to compile the latest source of
>>> mesa from the GIT repository in MS visual c++ 2005. As I seem to always
>>> have problems while others do not, it is probably something that I'm
>>> doing wrong.
>> Try removing swizzle.c from your project file.  It shouldn't be there.
>>
>> Don't know about the other errors.
>>
>> -Brian
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword
>> _______________________________________________
>> Mesa3d-users mailing list
>> Mes...@li...
>> https://lists.sourceforge.net/lists/listinfo/mesa3d-users
>>
> .
> 

Re: [Mesa3d-users] Mesa 7.3 release candidate 1

[Karl S. <kar...@gm...>]

Brian,

Did anyone submit a new project file for Visual Studio?  If not, I can
make one later this evening using the latest RC build.  Let me know.

Karl


On Wed, Jan 14, 2009 at 12:08 PM, Brian Paul <br...@vm...> wrote:
> Littlebob wrote:
>> I'm getting several errors while trying to compile the latest source of
>> mesa from the GIT repository in MS visual c++ 2005. As I seem to always
>> have problems while others do not, it is probably something that I'm
>> doing wrong.
>
> Try removing swizzle.c from your project file.  It shouldn't be there.
>
> Don't know about the other errors.
>
> -Brian
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Mesa3d-users mailing list
> Mes...@li...
> https://lists.sourceforge.net/lists/listinfo/mesa3d-users
>

Re: [Mesa3d-users] Mesa 7.3 release candidate 1

[Brian P. <br...@vm...>]

Littlebob wrote:
> I'm getting several errors while trying to compile the latest source of 
> mesa from the GIT repository in MS visual c++ 2005. As I seem to always 
> have problems while others do not, it is probably something that I'm 
> doing wrong.

Try removing swizzle.c from your project file.  It shouldn't be there.

Don't know about the other errors.

-Brian

Re: [Mesa3d-users] Mesa 7.3 release candidate 1

[Littlebob <lit...@gm...>]

I'm getting several errors while trying to compile the latest source of mesa
from the GIT repository in MS visual c++ 2005. As I seem to always have
problems while others do not, it is probably something that I'm doing wrong.


Lines with errors:
>>> swizzle.c
>>> c1 : fatal error C1083: Cannot open source file:
'..\..\..\..\src\mesa\main\swizzle.c': No such file or directory

...

>>> slang_compile.c
>>>  ..\..\..\..\src\mesa\shader\slang\slang_compile.c(1475) : error C2275:
'slang_operation' : illegal use of this type as an expression
>>>
..\..\..\..\src\mesa\shader\slang\slang_compile_operation.h(130) : see
declaration of 'slang_operation'
>>> ..\..\..\..\src\mesa\shader\slang\slang_compile.c(1475) : error C2146:
syntax error : missing ';' before identifier 'array_size'
>>> ..\..\..\..\src\mesa\shader\slang\slang_compile.c(1475) : error C2065:
'array_size' : undeclared identifier
>>> ..\..\..\..\src\mesa\shader\slang\slang_compile.c(1476) : warning C4133:
'function' : incompatible types - from 'int *' to 'slang_operation *'
>>> ..\..\..\..\src\mesa\shader\slang\slang_compile.c(1477) : warning C4133:
'function' : incompatible types - from 'int *' to 'slang_operation *'
>>> ..\..\..\..\src\mesa\shader\slang\slang_compile.c(1478) : warning C4133:
'function' : incompatible types - from 'int *' to 'slang_operation *'
>>> ..\..\..\..\src\mesa\shader\slang\slang_compile.c(1481) : error C2224:
left of '.type' must have struct/union type
>>> ..\..\..\..\src\mesa\shader\slang\slang_compile.c(1484) : warning C4133:
'function' : incompatible types - from 'int *' to 'slang_operation *'
>>> ..\..\..\..\src\mesa\shader\slang\slang_compile.c(1487) : error C2224:
left of '.literal' must have struct/union type
>>> ..\..\..\..\src\mesa\shader\slang\slang_compile.c(1489) : warning C4133:
'function' : incompatible types - from 'int *' to 'slang_operation *'


Thanks

Re: [Mesa3d-users] Mesa 7.3 release candidate 1

[Brian P. <br...@vm...>]

Thomas Henn wrote:
> Brian Paul <brianp@vm...> writes:
>  > Please report any issues/bugs ASAP. Thanks.
> 
> In VC8, the following files are missing in mesa.vcproj:
> src\mesa\glapi\glapi_getproc.c
> src\mesa\tnl\t_rasterpos.c
> src\mesa\shader\prog_cache.c
> src\mesa\main\scissor.c
> src\mesa\main\pixelstore.c
> src\mesa\main\multisample.c
> src\mesa\main\api_exec.c
> ...and some more...

OK, I've added these and some others.  I can't test on Windows though so 
I'd appreciate getting a new mesa.vcproj file from you or someone.


> Besides, the following module definition should be used in glut.vcproj:
> src\glut\glx\glut.def

Can you send me a new glut.vcproj file?

-Brian

Re: [Mesa3d-users] Mesa 7.3 release candidate 1

[Brian P. <bri...@tu...>]

tom fogal wrote:
> Brian Paul <br...@vm...> writes:
>> Please report any issues/bugs ASAP.  Thanks.
> 
> src/mesa/osmesa.pc.in appears to be missing:
> 
>     make[6]: Leaving directory `.../Mesa-7.3-rc1/src/mesa/drivers/osmesa'
>     make[5]: Leaving directory `.../Mesa-7.3-rc1/src/mesa/drivers/osmesa'
>     make[4]: Leaving directory `.../Mesa-7.3-rc1/src/mesa/drivers'
>     make[3]: *** No rule to make target `osmesa.pc.in', needed by `osmesa.pc'.  Stop.
> 
> configured with:
> 
>     ./configure                        \
>         CFLAGS="-DUSE_MGL_NAMESPACE"   \
>         CXXFLAGS="-DUSE_MGL_NAMESPACE" \
>         --prefix=${HOME}/sw/m73        \
>         --with-driver=xlib
> 
> Appears to be present in my git tree, so perhaps a distribution issue?

Fixed.  Thanks.

-Brian

Re: [Mesa3d-users] Mesa 7.3 release candidate 1

[Thomas H. <tho...@ig...>]

Brian Paul <brianp@vm...> writes:
 > Please report any issues/bugs ASAP. Thanks.

In VC8, the following files are missing in mesa.vcproj:
src\mesa\glapi\glapi_getproc.c
src\mesa\tnl\t_rasterpos.c
src\mesa\shader\prog_cache.c
src\mesa\main\scissor.c
src\mesa\main\pixelstore.c
src\mesa\main\multisample.c
src\mesa\main\api_exec.c
...and some more...

Besides, the following module definition should be used in glut.vcproj:
src\glut\glx\glut.def

Thomas

Re: [Mesa3d-users] Help: libdrm problem

[Sergio M. B. <se...@se...>]

On Mon, 2009-01-12 at 09:59 +0800, Lee Amy wrote:
> 2009/1/12 Sergio Monteiro Basto <se...@se...>:
> > On Sun, 2009-01-11 at 11:36 +0800, Lee Amy wrote:
> >> I'm going to compile the Mesa 7.2 for installing a bioinformatics
> >> software called VMD
> >
> > VMD needs Mesa ultimate sources ?
> > if not Cent OS came with Mesa already !
> >
> > Regards,
> > --
> > Sérgio M. B.
> >
> 
> Thanks. As I know before, just from Fedora 9 redhat provides mesa
> package, so my Cent OS is based on RHEL 4, cannot in the support list.
> 
> Anyway, when I compile the VMD it tells me that cannot find some files
> who belongs to mesa.
> 
> So do you have any good idea?

install something like: xorg-x11-devel-6.8.2 
and 
mesa-libGL
mesa-libGL-devel
mesa-libGLU
mesa-libGLU-devel
mesa-libOSMesa
mesa-libOSMesa-devel
or something similar

> 
> Regards,
> 
> Amy
regards
-- 
Sérgio M. B.

Re: [Mesa3d-users] Help: libdrm problem

[Lee A. <ope...@gm...>]

2009/1/12 Sergio Monteiro Basto <se...@se...>:
> On Sun, 2009-01-11 at 11:36 +0800, Lee Amy wrote:
>> I'm going to compile the Mesa 7.2 for installing a bioinformatics
>> software called VMD
>
> VMD needs Mesa ultimate sources ?
> if not Cent OS came with Mesa already !
>
> Regards,
> --
> Sérgio M. B.
>

Thanks. As I know before, just from Fedora 9 redhat provides mesa
package, so my Cent OS is based on RHEL 4, cannot in the support list.

Anyway, when I compile the VMD it tells me that cannot find some files
who belongs to mesa.

So do you have any good idea?

Regards,

Amy

Re: [Mesa3d-users] Help: libdrm problem

[Sergio M. B. <se...@se...>]

On Sun, 2009-01-11 at 11:36 +0800, Lee Amy wrote:
> I'm going to compile the Mesa 7.2 for installing a bioinformatics
> software called VMD

VMD needs Mesa ultimate sources ?
if not Cent OS came with Mesa already !

Regards, 
-- 
Sérgio M. B.

Re: [Mesa3d-users] Help: libdrm problem

[Lee A. <ope...@gm...>]

2009/1/11 Erik Boettcher <te...@gm...>:
> On Sat, Jan 10, 2009 at 11:20 PM, Sergio Monteiro Basto
> <se...@se...> wrote:
>> locate libdrm.pc
>>
>
> There is no libdrm.pc with that package which is why distros like
> gentoo provide it.
>
> - Erik Boettcher
>

Thanks, it seems that libdrm configuration is okay, but I encountered
another problem, when I run 'gmake', it shows following error
messages.

gmake[1]: Entering directory `/root/Mesa-7.2/src'
Making sources for autoconf
gmake[2]: Entering directory `/root/Mesa-7.2/src/glx/x11'
gcc -c -I. -I../../../include -I../../../include/GL/internal
-I../../../src/mesa/main -I../../../src/mesa/glapi -I/usr/include/drm
 -I/usr/X11R6/include -g -O2 -Wall -Wmissing-prototypes -std=c99
-ffast-math -fno-strict-aliasing  -fPIC  -DUSE_X86_ASM -DUSE_MMX_ASM
-DUSE_3DNOW_ASM -DUSE_SSE_ASM -D_POSIX_SOURCE
-D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE
-DPTHREADS -DHAVE_POSIX_MEMALIGN -DUSE_EXTERNAL_DXTN_LIB=1
-DIN_DRI_DRIVER -DGLX_INDIRECT_RENDERING -DHAVE_ALIAS
-DGLX_DIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER
-DDEFAULT_DRIVER_DIR=\"/usr/local/lib/dri\" glxcmds.c -o glxcmds.o
glxcmds.c:113: error: syntax error before "__GLXDRIdrawable"
glxcmds.c:486: error: syntax error before "void"
glxcmds.c:2160: error: syntax error before "GLboolean"
glxcmds.c:2238: error: syntax error before "GLboolean"
glxcmds.c: In function `__glXBindTexImageEXT':
glxcmds.c:2600: error: `X_GLXvop_BindTexImageEXT' undeclared (first
use in this function)
glxcmds.c:2600: error: (Each undeclared identifier is reported only once
glxcmds.c:2600: error: for each function it appears in.)
glxcmds.c: In function `__glXReleaseTexImageEXT':
glxcmds.c:2652: error: `X_GLXvop_ReleaseTexImageEXT' undeclared (first
use in this function)
glxcmds.c: At top level:
glxcmds.c:2672: error: syntax error before "char"
glxcmds.c:2913: error: syntax error before "int"
gmake[2]: *** [glxcmds.o] Error 1
gmake[2]: Leaving directory `/root/Mesa-7.2/src/glx/x11'
gmake[1]: *** [subdirs] Error 1
gmake[1]: Leaving directory `/root/Mesa-7.2/src'
gmake: *** [default] Error 1

What happened? I use GeForce 2 MX 400 and I have installed nvidia
driver properly.

Thanks.

Amy

Re: [Mesa3d-users] Help: libdrm problem

[Erik B. <te...@gm...>]

On Sat, Jan 10, 2009 at 11:20 PM, Sergio Monteiro Basto
<se...@se...> wrote:
> locate libdrm.pc
>

There is no libdrm.pc with that package which is why distros like
gentoo provide it.

- Erik Boettcher

Re: [Mesa3d-users] Help: libdrm problem

[Sergio M. B. <se...@se...>]

On Sun, 2009-01-11 at 11:36 +0800, Lee Amy wrote:
> Hello,
> 
> I'm going to compile the Mesa 7.2 for installing a bioinformatics
> software called VMD. I notice that Mesa needs libdrm so I download the
> libdrm package from dri.freedesktop.org/libdrm. I use the version of
> 2.4.3.
> 
> Libdrm complied and installed well, then when I do configuration Mesa
> shows following error messages.
> 
> checking for LIBDRM... Package libdrm was not found in the pkg-config
> search path.
> Perhaps you should add the directory containing `libdrm.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'libdrm' found
> configure: error: Package requirements (libdrm >= 2.3.1) were not met:
> 
> 
> 
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
> 
> Alternatively, you may set the environment variables LIBDRM_CFLAGS
> and LIBDRM_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> 
> However, I suppose that I have installed such package, so I don't know
> how to go on. Could anyone how to fix that problem? My OS is Cent OS
> 4.7 with kernel version of 2.6.9-78.EL.

find where is installed libdrm.pc 

locate libdrm.pc

and do a 
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig/
according where you find libdrm.pc

Regards, 
-- 
Sérgio M. B.

Re: [Mesa3d-users] Help: libdrm problem

[Erik B. <te...@gm...>]

On Sat, Jan 10, 2009 at 10:36 PM, Lee Amy <ope...@gm...> wrote:
> checking for LIBDRM... Package libdrm was not found in the pkg-config
> search path.
> Perhaps you should add the directory containing `libdrm.pc'
> to the PKG_CONFIG_PATH environment variable

Hi, Amy
Attached is a file that usualy goes in /usr/lib/pkgconfig but you can
put it anywhere
in PKG_CONFIG_PATH.  Adjust prefix and libdir to match what you used for for the
configure script.  On most systems this is "prefix = /usr" and "libdir
= /usr/lib".

- Erik Boettcher

[Mesa3d-users] Help: libdrm problem

[Lee A. <ope...@gm...>]

Hello,

I'm going to compile the Mesa 7.2 for installing a bioinformatics
software called VMD. I notice that Mesa needs libdrm so I download the
libdrm package from dri.freedesktop.org/libdrm. I use the version of
2.4.3.

Libdrm complied and installed well, then when I do configuration Mesa
shows following error messages.

checking for LIBDRM... Package libdrm was not found in the pkg-config
search path.
Perhaps you should add the directory containing `libdrm.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libdrm' found
configure: error: Package requirements (libdrm >= 2.3.1) were not met:



Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables LIBDRM_CFLAGS
and LIBDRM_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

However, I suppose that I have installed such package, so I don't know
how to go on. Could anyone how to fix that problem? My OS is Cent OS
4.7 with kernel version of 2.6.9-78.EL.

Thank you very much.

Best Regards,

Amy Lee

Re: [Mesa3d-users] Mesa 7.3 release candidate 1

[tom f. <tf...@al...>]

Brian Paul <br...@vm...> writes:
> Please report any issues/bugs ASAP.  Thanks.

src/mesa/osmesa.pc.in appears to be missing:

    make[6]: Leaving directory `.../Mesa-7.3-rc1/src/mesa/drivers/osmesa'
    make[5]: Leaving directory `.../Mesa-7.3-rc1/src/mesa/drivers/osmesa'
    make[4]: Leaving directory `.../Mesa-7.3-rc1/src/mesa/drivers'
    make[3]: *** No rule to make target `osmesa.pc.in', needed by `osmesa.pc'.  Stop.

configured with:

    ./configure                        \
        CFLAGS="-DUSE_MGL_NAMESPACE"   \
        CXXFLAGS="-DUSE_MGL_NAMESPACE" \
        --prefix=${HOME}/sw/m73        \
        --with-driver=xlib

Appears to be present in my git tree, so perhaps a distribution issue?

-tom

[Mesa3d-users] Mesa 7.3 release candidate 1

[Brian P. <br...@vm...>]

Can be downloaded from http://www.mesa3d.org/beta/

The included docs/relnotes-7.3.html file lists the changes.

Please report any issues/bugs ASAP.  Thanks.

-Brian

[Mesa3d-users] Mesa dependecies

[Angel T. <fn...@fm...>]

Guys,

Can someone tell what the dependencies of Mesa 6.5.3 or 7.2 are (both w/o 
DRI)?  I suspect both versions have a lot of dependencies among the various 
X.org packages.  Do I need to install all of them 'by hand'?!

Regards,
Angel Tsankov 

Re: [Mesa3d-users] general question

[keithw <ke...@vm...>]

On Tue, 2009-01-06 at 20:46 -0800, Daniel Hoggan wrote:
> I wanted to use mesa3d in my program, however, I only need mesas'
> OpenGL rendering functionality, I don't need it's device drivers, or
> any hardware support as this comes from other code in my program, so
> could someone answer my questions:
> 
> 1) tnl_dd are device drivers for the tnl module right?, do I require
> them for mesa to work properly or can I remove that module, and vbo?
> 2) what is VBO, and do I require it, I aim to make the mesa library as
> small as possible whilst still retaining the full functionality.
> 3) I removed swrast_setup is this ok?
> 4) I basically want to know what is alright to remove and what isn't
> in order to make the mesa library as small as possible, while still
> keeping the rendering functionality, but I can definately remove the
> device drivers, unless there is somewhere in the code that actually
> positively requires them, but there shouldn't be right?

It's a bit confusing.  These directories aren't strictly required, but
if you omitted them you'd have to provide alternate implementations of
the functionality they provide.

The quick answer is that you'll want vbo/ and probably tnl/, and then
whatever else you need to get compilation working.

I'm guessing you'll need the following:
  vbo -- listens to things like glVertex3f, glCallList, accumulates them
into a single vbo-based rendering path that can be handed off to drivers
or software tnl modules.
  tnl -- a software tnl module
  main -- core mesa
  shader -- a mix of core mesa shader support and a software shader
implementation.  The core mesa stuff should really move into main/
  glapi -- the GL dispatch layer


But probably not these:
  x86, sparc, ppc -- assembly-based fastpaths
  vf -- helpers for drivers building hw vertices.
  tnl_dd -- bunch of old helpers for drivers that relied on tnl/ module
  swrast_setup - helper for drivers using swrast fallbacks
  swrast -- software rasterizer
  math -- old maths routines, probably referenced from tnl/
  
Keith

Re: [Mesa3d-users] [PATCH] Add mangled symbols to export list.

[Brian P. <br...@vm...>]

tom fogal wrote:
> From: Tom Fogal <tf...@al...>
> 
> This adds all of the `mglu' symbols to the list of symbol exports
> for GLU.  Without this patch, mangled GLU symbols are considered
> `internal' symbols, and calling any results in undefined
> references.

Committed.  Thanks.

-Brian

[Mesa3d-users] [PATCH] Add mangled symbols to export list.

[tom f. <tf...@al...>]

From: Tom Fogal <tf...@al...>

This adds all of the `mglu' symbols to the list of symbol exports
for GLU.  Without this patch, mangled GLU symbols are considered
`internal' symbols, and calling any results in undefined
references.
---
 src/glu/sgi/glu.exports |   59 +++++++++++++++++++++++++++++++++++++++++++++++
 1 files changed, 59 insertions(+), 0 deletions(-)

diff --git a/src/glu/sgi/glu.exports b/src/glu/sgi/glu.exports
index 1d1b6da..aeb7272 100644
--- a/src/glu/sgi/glu.exports
+++ b/src/glu/sgi/glu.exports
@@ -57,3 +57,62 @@
 	gluTessVertex
 	gluUnProject
 	gluUnProject4
+	mgluBeginCurve
+	mgluBeginPolygon
+	mgluBeginSurface
+	mgluBeginTrim
+	mgluBuild1DMipmapLevels
+	mgluBuild1DMipmaps
+	mgluBuild2DMipmapLevels
+	mgluBuild2DMipmaps
+	mgluBuild3DMipmapLevels
+	mgluBuild3DMipmaps
+	mgluCheckExtension
+	mgluCylinder
+	mgluDeleteNurbsRenderer
+	mgluDeleteQuadric
+	mgluDeleteTess
+	mgluDisk
+	mgluEndCurve
+	mgluEndPolygon
+	mgluEndSurface
+	mgluEndTrim
+	mgluErrorString
+	mgluGetNurbsProperty
+	mgluGetString
+	mgluGetTessProperty
+	mgluLoadSamplingMatrices
+	mgluLookAt
+	mgluNewNurbsRenderer
+	mgluNewQuadric
+	mgluNewTess
+	mgluNextContour
+	mgluNurbsCallback
+	mgluNurbsCallbackData
+	mgluNurbsCallbackDataEXT
+	mgluNurbsCurve
+	mgluNurbsProperty
+	mgluNurbsSurface
+	mgluOrtho2D
+	mgluPartialDisk
+	mgluPerspective
+	mgluPickMatrix
+	mgluProject
+	mgluPwlCurve
+	mgluQuadricCallback
+	mgluQuadricDrawStyle
+	mgluQuadricNormals
+	mgluQuadricOrientation
+	mgluQuadricTexture
+	mgluScaleImage
+	mgluSphere
+	mgluTessBeginContour
+	mgluTessBeginPolygon
+	mgluTessCallback
+	mgluTessEndContour
+	mgluTessEndPolygon
+	mgluTessNormal
+	mgluTessProperty
+	mgluTessVertex
+	mgluUnProject
+	mgluUnProject4
-- 
1.6.0.4

[Mesa3d-users] missing semicolon in r300_render.c

[Beso <giv...@gm...>]

i've found out a missing semicolon in the r300_render.c file of mesa
dri drivers.
here's the patch to fix it up.

-- 
dott. ing. beso