mesa3d-users

[Mesa3d-users] My New Site

[Aaron J. <jaj...@ho...>]

OpenGL, Visit if you want, nothing about MESA, yet



Aaron
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

Re: [Mesa3d-users] 3D-NOW and Mesa

[physic <ph...@te...>]

Michel,

There has been 3d-now code in mesa for ages.  I'm not sure how well it has
been maintained but I don't remember people complaining about it breaking
recently.  You could certainly give it a try.  It might be good to test it
anyway on the 3.2 beta to make sure its ok before 3.2 becomes finalized,
which could be any day now.  You should be able to comile mesa with 3dnow
support by using: 'make -f Makefile.X11 linux-3dnow' or variations
thereof.

On Tue, 11 Apr 2000, Michel N. Fodje wrote:

> Hi all,
> Is there any support for 3D-NOW in mesa, if so how does one activate it
> ?
> 
> --
> ________________________________________________________(________
> Dept. of Molecular Biophysics,                           )
> Center for Chemistry and Chem. Engineering
> Lund University, Box 124, S-22100, Sweden.  Tel: +46(0)46 2224566
> 
> 
> 
> 
> _______________________________________________
> Mesa3d-users mailing list
> Mes...@li...
> http://lists.sourceforge.net/mailman/listinfo/mesa3d-users
> 

--physic
ph...@te...

[Mesa3d-users] 3D-NOW and Mesa

[Michel N. F. <mic...@mb...>]

Hi all,
Is there any support for 3D-NOW in mesa, if so how does one activate it
?

--
________________________________________________________(________
Dept. of Molecular Biophysics,                           )
Center for Chemistry and Chem. Engineering
Lund University, Box 124, S-22100, Sweden.  Tel: +46(0)46 2224566

Re: [Mesa3d-users] Help in basics of Mesa/OpenGL

[physic <ph...@te...>]

> I recently upgraded to Xfree86 4.0, and I noticed the GL architecture has
> changed...
> I had Mesa 3.0 installed in /usr/lib, and now, X has it's own installed in
> /usr/X11R4/lib.

This was a mistake in xf4.  Should be fixed for the next release.

> I understand the libGL.so that comes with X4 is Mesa 3.3beta? Yet, I cannot
> find Mesa3.3anything, even under the Mesa CVS. I would just use the libGL

The 3.3 branch is the default cvs branch.  No official beta was released
expect the code dump that went into the xf4 release.

> My question is, what can I do to get Mesa/GL working under X4?

Have a little more patience I think.  Its still a bit difficult.  Check
the dri list archive for all the recent people trying ot get it to work.

> - I would try upgrading to Mesa3.3beta if I could find it, but I was
> recently informed that it's not stock mesa that comes with X4, but an
> altered version....

It is the 3.3 branch compiled a certain way.  You really wad to visit the
dri people at dri.sourceforge.net.  They are integrating mesa into xf4.

> I was also interested if/when the GLX project will be incorperated in Mesa?
> I understand they have support for the agp module in the new kernel...

The utah-glx code is separate from the dri priject, but many developers
contribute to both.  My feeling is that the dri stuff will get working and
everyone will just start using and developing with that since it works
well with xf4.  Who knows for sure though.  I dont think the utah-glx
people even know what they want to do yet.

--physic
ph...@te...

Re: [Mesa3d-users] Help in basics of Mesa/OpenGL

[Paul de R. <de...@ac...>]

Igor Evdokimov wrote:

> Can anybody help me in general of Mesa/OpenGL?
> I'm novice with Mesa and other 3d programming.
>

Ahh... so life does exist on this list :>

I recently upgraded to Xfree86 4.0, and I noticed the GL architecture has
changed...
I had Mesa 3.0 installed in /usr/lib, and now, X has it's own installed in
/usr/X11R4/lib.
I understand the libGL.so that comes with X4 is Mesa 3.3beta? Yet, I cannot
find Mesa3.3anything, even under the Mesa CVS. I would just use the libGL
that comes with X, except that it doesn not include libGLU and the libGL
doesn't include support for ggi or glut or anything nifty like that, and it
lacks alot of needed header files, though it does include some.

My question is, what can I do to get Mesa/GL working under X4?
- I would try upgrading to Mesa3.3beta if I could find it, but I was
recently informed that it's not stock mesa that comes with X4, but an
altered version....

I was also interested if/when the GLX project will be incorperated in Mesa?
I understand they have support for the agp module in the new kernel...

Thanks for any help or comments :>

--
+-Ax0n--[Paul de Regt]--(de...@ac...)---------+
| #include <disclaimer.h>                             |
| PGP ID 0xC9E64E52                     ICQ# 25840522 |
+-[B78F 3B4D 117D FAF2 C343 F926 AB01 3FD9 2D1C 765D]-+
|      I of course have zero evidence for this,       |
|     but since when has that stopped any of us?      |
+-----------------------------------------------------+

Re: [Mesa3d-users] Help in basics of Mesa/OpenGL

[Stephen J B. <sj...@ht...>]

On Mon, 10 Apr 2000, Igor Evdokimov wrote:

> The libraries - libGL, libGLU, libGLUT, libGLX.
> 
> 1) What does every one of them do? What are the main functions?
 
libGL contains all the functions whose names begin with 'gl', the
      basic core of OpenGL functions.

libGLU contains some utility functions for doing things like
      tessellation, spline curves, etc.  All the functions whose
      names start with 'glu'.  GLU functions are not part of the
      OpenGL core API and may be omitted.  Generally, GLU functions
      only make calls to libGL.

libglut (not usually capitalised) is another GL utility toolkit
      called 'GLUT' that provides a device independent window
      management/mouse/keyboard/joystick interface.  These functions
      are not at all a part of the OpenGL specification - but are
      used (for example) for the sample code in the OpenGL user
      guide.  GLUT routines all start with the letters 'glut' (Suprise,
      suprise!)

GLX (not libGLX) is two things:

      * Specifically for X-window systems there are a bunch of 'glX'
        functions in libGL that contain all the routines that a
        program needs in order to interface with X windows.

      * An interface protocol that allows OpenGL programs running
        on one computer to produce graphics on another - providing
        both support the GLX protocol.  In a sense, this is like
        X-window's ability to do the same thing.

> The second question is -
> 
> 2) We need to make industrial (mining & geology) 3d-modelling software
>  (under QPL or GNU GPL). What combination of
>  <GUI API>+<3D high-level library> you can advice me to make our software
>  better and faster? (We plan to use Mesa as an OpenGL API).
 
Well, I've had lots of success with FLTK (Fast-Light ToolKit)...there are
plenty of others to choose from though.  I don't know your application
area well enough to know what higher-level library you need for 3D work,
I'd be suprised if OpenGL (Mesa) were not good enough for your needs.

For example: The PPE 3D modeller for Linux is written using FLTK and Mesa.

             http://prettypoly.sourceforge.net

> You can answer me in Russian too.
 
No - I can't   :-(

Steve Baker                      (817)619-2657 (Vox/Vox-Mail)
L3Com/Link Simulation & Training (817)619-2466 (Fax)
Work: sj...@ht...            http://www.hti.com
Home: sjb...@ai...       http://web2.airmail.net/sjbaker1

Re: [Mesa3d-users] Help in basics of Mesa/OpenGL

[physic <ph...@te...>]

> The question is about architecture of OpenGL.
> 
> The libraries - libGL, libGLU, libGLUT, libGLX.

- libGL are the OpenGL core functions.  This is mostly what ones
uses in a accelerated 3d app.

- libGLU is a utility library defined by the opengl people.  Pretty
much every opengl implemention has it.  it just calls the functions
in libGL.  these routines are generally slow and shouldnt be put into
a time critical loop.

- libGLUT is an opengl graphical programming toolkit originally designed
by Mark Kilgard (now at nVidia) and has proved very used for demoing
OpenGL functionality because it hides the native windowing code.

- libGLX doesnt exist.  the GLX function are the routines that integrate
opengl into an X windows system.  these routines are generally in libGL
for that platform I think.  WGL is the microsodt windows alternative.

> 2) We need to make industrial (mining & geology) 3d-modelling software
>  (under QPL or GNU GPL). What combination of
>  <GUI API>+<3D high-level library> you can advice me to make our software
>  better and faster? (We plan to use Mesa as an OpenGL API).

Assuming you are using unix/linux, there are lots of choices.  Qt are Gtk
are both pretty feature right and more or less complete.  Certainly they
will work fine to wrap your 3d window.  As long as you are programming
your 3d stuff with the opengl spec then Mesa or any opengl library that
implements the spec will work with your program.

> Igor Evdokimov

--physic
ph...@te...

[Mesa3d-users] Help in basics of Mesa/OpenGL

[Igor E. <ig...@on...>]

Can anybody help me in general of Mesa/OpenGL?
I'm novice with Mesa and other 3d programming.

The question is about architecture of OpenGL.

The libraries - libGL, libGLU, libGLUT, libGLX.

1) What does every one of them do? What are the main functions?

The second question is -

2) We need to make industrial (mining & geology) 3d-modelling software
 (under QPL or GNU GPL). What combination of
 <GUI API>+<3D high-level library> you can advice me to make our software
 better and faster? (We plan to use Mesa as an OpenGL API).

You can answer me in Russian too.

Thanks.
-- 
Best regards,
Igor Evdokimov

╘IGEV	ig...@on...

[Mesa3d-users] Re: Too slow...

[Dmitry S. <sin...@ac...>]

I wrote:

>  I have a problem with Mesa-3.1(3.2) software rendering on Linux. My
>  application works fine on 3.0 but very slow on 3.1(3.2). I can't find a
>  cause of this problem. Can somebody help me?

Thank you for your answers!
I was discovered a cause of my problem. It was a filtration mode
(GL_NEAREST
and GL_LINEAR).
I have a following results of experiments with my program:

Mesa-3.0, GL_NEAREST:   8..9 FPS
Mesa-3.0, GL_LINEAR:   7 FPS
Mesa-3.1, GL_NEAREST:   6 FPS
Mesa-3.1, GL_LINEAR:   3 FPS

The libraries was builded "as is" (without any additional options).
I don't understand why GL_LINEAR working so slow on 3.1.

[Mesa3d-users] Bug database usage

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

I'm glad that people are reporting bugs in the Mesa bug database
on SourceForge.  However, I'd like it if people would submit their
bugs as a real user, not anonymously.  If you submit bugs anonymously
you won't get email when the report is modified.  People usually don't
submit enough information in their bug reports and I have to ask
follow-up questions.  If you report bugs as anonymous, please
check back every so often to see if more information is needed.

Remember, a vague bug report is pretty much worthless and is unlikely
to get fixed.

Thanks.

-Brian

Re: [Mesa3d-users] Re: Mesa3d-users digest, Vol 1 #9 - 2 msgs

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

Alberto Farré wrote:
> 
> mes...@li... wrote:
> 
> > Send Mesa3d-users mailing list submissions to
> >         mes...@li...
> >
> > To subscribe or unsubscribe via the web, visit
> >         http://lists.sourceforge.net/mailman/listinfo/mesa3d-users
> > or, via email, send a message with subject or body 'help' to
> >         mes...@li...
> > You can reach the person managing the list at
> >         mes...@li...
> >
> > When replying, please edit your Subject line so it is more specific than
> > "Re: Contents of Mesa3d-users digest..."
> >
> > Today's Topics:
> >
> >   1. Too slow... (Dmitry Samoyloff)
> >   2. Re: Too slow... (physic)
> >
> > --__--__--
> >
> > Message: 1
> > Date: Wed, 05 Apr 2000 04:41:04 +0400
> > From: Dmitry Samoyloff <sin...@ac...>
> > Organization: Actor
> > To: mes...@li...
> > Subject: [Mesa3d-users] Too slow...
> >
> > Hello!
> >
> > I have a problem with Mesa-3.1(3.2) software rendering on Linux. My
> > application works fine on 3.0 but very slow on 3.1(3.2). I can't find a
> > cause of this problem. Can somebody help me?
> >
> > Thank you very much!
> >
> > --__--__--
> >
> > Message: 2
> > Date: Tue, 4 Apr 2000 20:50:41 -0500 (CDT)
> > From: physic <ph...@te...>
> > To: Dmitry Samoyloff <sin...@ac...>
> > cc: mes...@li...
> > Subject: Re: [Mesa3d-users] Too slow...
> >
> > Have you tried the demos that come with the different versions.  The demos
> > that are fairly simple will help determine if it is some rendering path in
> > your code that got slowed down (or probably fully implemented) or
> > something more related to how they were built.
> >
> > On Wed, 5 Apr 2000, Dmitry Samoyloff wrote:
> >
> > > Hello!
> > >
> > > I have a problem with Mesa-3.1(3.2) software rendering on Linux. My
> > > application works fine on 3.0 but very slow on 3.1(3.2). I can't find a
> > > cause of this problem. Can somebody help me?
> > >
> > > Thank you very much!
> > >
> > > _______________________________________________
> > > Mesa3d-users mailing list
> > > Mes...@li...
> > > http://lists.sourceforge.net/mailman/listinfo/mesa3d-users
> > >
> >
> > --physic
> > ph...@te...
> >
> > --__--__--
> >
> > _______________________________________________
> > Mesa3d-users mailing list
> > Mes...@li...
> > http://lists.sourceforge.net/mailman/listinfo/mesa3d-users
> >
> > End of Mesa3d-users Digest
> 
> I had the same problem and  I needed to remove the following lines:
> glEnable(GL_NORMALIZE)
> glPolygonMode(GL_BACK,GL_POINT)
> 
> Does it fix your problem?
> Does anyone known why I had to remove those lines to rescue normal speed in
> application?

The slowdown of glPolygonMode on the 3dfx is a known problem, and
in the bug database.  I don't know when it'll be fixed.

There shouldn't be a really significant slowdown from enabling
GL_NORMALIZE.

-Brian

[Mesa3d-users] Re: Mesa3d-users digest, Vol 1 #9 - 2 msgs

[Alberto <sp...@re...>]

mes...@li... wrote:

> Send Mesa3d-users mailing list submissions to
>         mes...@li...
>
> To subscribe or unsubscribe via the web, visit
>         http://lists.sourceforge.net/mailman/listinfo/mesa3d-users
> or, via email, send a message with subject or body 'help' to
>         mes...@li...
> You can reach the person managing the list at
>         mes...@li...
>
> When replying, please edit your Subject line so it is more specific than
> "Re: Contents of Mesa3d-users digest..."
>
> Today's Topics:
>
>   1. Too slow... (Dmitry Samoyloff)
>   2. Re: Too slow... (physic)
>
> --__--__--
>
> Message: 1
> Date: Wed, 05 Apr 2000 04:41:04 +0400
> From: Dmitry Samoyloff <sin...@ac...>
> Organization: Actor
> To: mes...@li...
> Subject: [Mesa3d-users] Too slow...
>
> Hello!
>
> I have a problem with Mesa-3.1(3.2) software rendering on Linux. My
> application works fine on 3.0 but very slow on 3.1(3.2). I can't find a
> cause of this problem. Can somebody help me?
>
> Thank you very much!
>
> --__--__--
>
> Message: 2
> Date: Tue, 4 Apr 2000 20:50:41 -0500 (CDT)
> From: physic <ph...@te...>
> To: Dmitry Samoyloff <sin...@ac...>
> cc: mes...@li...
> Subject: Re: [Mesa3d-users] Too slow...
>
> Have you tried the demos that come with the different versions.  The demos
> that are fairly simple will help determine if it is some rendering path in
> your code that got slowed down (or probably fully implemented) or
> something more related to how they were built.
>
> On Wed, 5 Apr 2000, Dmitry Samoyloff wrote:
>
> > Hello!
> >
> > I have a problem with Mesa-3.1(3.2) software rendering on Linux. My
> > application works fine on 3.0 but very slow on 3.1(3.2). I can't find a
> > cause of this problem. Can somebody help me?
> >
> > Thank you very much!
> >
> > _______________________________________________
> > Mesa3d-users mailing list
> > Mes...@li...
> > http://lists.sourceforge.net/mailman/listinfo/mesa3d-users
> >
>
> --physic
> ph...@te...
>
> --__--__--
>
> _______________________________________________
> Mesa3d-users mailing list
> Mes...@li...
> http://lists.sourceforge.net/mailman/listinfo/mesa3d-users
>
> End of Mesa3d-users Digest

I had the same problem and  I needed to remove the following lines:
glEnable(GL_NORMALIZE)
glPolygonMode(GL_BACK,GL_POINT)

Does it fix your problem?
Does anyone known why I had to remove those lines to rescue normal speed in
application?

Re: [Mesa3d-users] Too slow...

[physic <ph...@te...>]

Have you tried the demos that come with the different versions.  The demos
that are fairly simple will help determine if it is some rendering path in
your code that got slowed down (or probably fully implemented) or
something more related to how they were built.


On Wed, 5 Apr 2000, Dmitry Samoyloff wrote:

> Hello!
> 
> I have a problem with Mesa-3.1(3.2) software rendering on Linux. My
> application works fine on 3.0 but very slow on 3.1(3.2). I can't find a
> cause of this problem. Can somebody help me?
> 
> Thank you very much!
> 
> _______________________________________________
> Mesa3d-users mailing list
> Mes...@li...
> http://lists.sourceforge.net/mailman/listinfo/mesa3d-users
> 

--physic
ph...@te...

[Mesa3d-users] Too slow...

[Dmitry S. <sin...@ac...>]

Hello!

I have a problem with Mesa-3.1(3.2) software rendering on Linux. My
application works fine on 3.0 but very slow on 3.1(3.2). I can't find a
cause of this problem. Can somebody help me?

Thank you very much!

Re: [Mesa3d-users] Mesa/DRI/XFree86 4.0 problem

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

John Wharington wrote:
> 
> 
> 
> Running some applications that use the Mesa-DRI-XFree86 4.0 combo on
> Voodoo3, get a black window.  When hardware rendering is disabled,
> the display looks fine.  The applications in question use the gizmo3d library,
> which is supposed to require Mesa with multithreading enabled.  Might this have
> something to do with the black display?

It might.  The tdfx driver isn't threadsafe at this point even though
the Mesa core is.


> I have searched on what the deal is with installing a new (e.g. CVS) Mesa for
> XFree86 4.0 but to no avail.  Any pointers?

I've *got* to write a FAQ on this.  Installing a new version of Mesa
inside of XFree86 4.0 is not for the faint of heart!  If you're lucky,
you can replace all the files in xc/extras/Mesa from newer versions
from Mesa CVS, recompile the X server's GLX module, recompile all DRI 3D
driver modules, recompile the libGL.so library (just to be safe) and it'll
work.  But since Mesa 3.3 is still under development I occasionally
introduce new source files and that requires modifying the XFree86
Imakefiles.  It's really easy to make a mistake there and get a variety
of problems as a result.

I don't recommend touching the Mesa sources inside XFree86 unless
you really know what you're doing.  I've been too busy to help people
that try this and get stuck.  Sorry.

-Brian

[Mesa3d-users] Mesa/DRI/XFree86 4.0 problem

[John W. <Joh...@de...>]

Running some applications that use the Mesa-DRI-XFree86 4.0 combo on
Voodoo3, get a black window.  When hardware rendering is disabled,
the display looks fine.  The applications in question use the gizmo3d
library,
which is supposed to require Mesa with multithreading enabled.  Might
this have
something to do with the black display?

I have searched on what the deal is with installing a new (e.g. CVS)
Mesa for
XFree86 4.0 but to no avail.  Any pointers?

Thanks,


John Wharington


--
 ___________________________________________________
|Dr John Wharington
|Research Scientist
|Maritime Platforms Division
|Aeronautical and Maritime Research Laboratories
|Defence Science Technology Organisation
|mailto: Joh...@ds...
!___________________________________________________

   "Jeet Kune Do favors formlessness so it can assume all forms and since Jeet Kune Do has no style, it can fit in with all styles. As a result,
   Jeet Kune Do utilizes all ways and is bound by none and, likewise, uses any techniques or means which serve its end."
   Bruce Lee.

Re: [Mesa3d-users] Configure file on Mesa-3.2

[physic <ph...@te...>]

The suggestion is not to use configure, but Makefile.X11 instead, until
someone starts maintaining the configure scripts again.


On Mon, 3 Apr 2000, M. Lavasani wrote:

> Hi 
> 
> Sorry about bothering you all!!
> 
> 
> I've been porting "Mesa" library for HPUX users for sometimes now.
> 
> I 've noticed when i compile the latest version of program using
> configure file
> the "pwd" in "ltconfig" and "ltmain.sh" files put my home path in the
> binaries.
> Therefore the HP usres that are going to use this binary will have
> problem.
> 
> Have you got any suggestion please?
> 
> Does it effect anything if i take the section below from "ltmain.sh"?
> I think that is where the problem coming from.
> 
> Thanks for your advise.
> 
> 		__Mehdi
> 
> ps. Sorry I am not part of this mailing list. Could you e_mail me if you
> have any suggestions please.
> lav...@co...
> 
> 
> 
> >           for xlib in $convenience; do
> >             # Extract the objects.
> >             case "$xlib" in
> >             [\\/]* | [A-Za-z]:[\\/]*) xabs="$xlib" ;;
> >             *) xabs=`pwd`"/$xlib" ;;
> >             esac
> >             xlib=`$echo "X$xlib" | $Xsed -e 's%^.*/%%'`
> >             xdir="$gentop/$xlib"
> 2124a2133,2145
> >             $show "${rm}r $xdir"
> >             $run ${rm}r "$xdir"
> >             $show "mkdir $xdir"
> >             $run mkdir "$xdir"
> >             status=$?
> >             if test $status -ne 0 && test ! -d "$xdir"; then
> >               exit $status
> >             fi
> >             $show "(cd $xdir && $AR x $xabs)"
> >             $run eval "(cd \$xdir && $AR x \$xabs)" || exit $?
> > 
> >             libobjs="$libobjs "`find $xdir -name \*.o -print -o -name \*.lo -print | $NL2SP`
> >           done
> 2235a2257,2264
> >         for xlib in $convenience; do
> >           # Extract the objects.
> >           case "$xlib" in
> >           [\\/]* | [A-Za-z]:[\\/]*) xabs="$xlib" ;;
> >           *) xabs=`pwd`"/$xlib" ;;
> >           esac
> >           xlib=`$echo "X$xlib" | $Xsed -e 's%^.*/%%'`
> >           xdir="$gentop/$xlib"
> 2236a2266,2278
> >           $show "${rm}r $xdir"
> >           $run ${rm}r "$xdir"
> >           $show "mkdir $xdir"
> >           $run mkdir "$xdir"
> >           status=$?
> >           if test $status -ne 0 && test ! -d "$xdir"; then
> >             exit $status
> >           fi
> >           $show "(cd $xdir && $AR x $xabs)"
> >           $run eval "(cd \$xdir && $AR x \$xabs)" || exit $?
> > 
> >           reload_conv_objs="$reload_objs "`find $xdir -name \*.o -print -o -name \*.lo -print | $NL2SP`
> >         done
> 
> _______________________________________________
> Mesa3d-users mailing list
> Mes...@li...
> http://lists.sourceforge.net/mailman/listinfo/mesa3d-users
> 

--physic
ph...@te...

[Mesa3d-users] Configure file on Mesa-3.2

[M. L. <lav...@co...>]

Hi 

Sorry about bothering you all!!


I've been porting "Mesa" library for HPUX users for sometimes now.

I 've noticed when i compile the latest version of program using
configure file
the "pwd" in "ltconfig" and "ltmain.sh" files put my home path in the
binaries.
Therefore the HP usres that are going to use this binary will have
problem.

Have you got any suggestion please?

Does it effect anything if i take the section below from "ltmain.sh"?
I think that is where the problem coming from.

Thanks for your advise.

		__Mehdi

ps. Sorry I am not part of this mailing list. Could you e_mail me if you
have any suggestions please.
lav...@co...



>           for xlib in $convenience; do
>             # Extract the objects.
>             case "$xlib" in
>             [\\/]* | [A-Za-z]:[\\/]*) xabs="$xlib" ;;
>             *) xabs=`pwd`"/$xlib" ;;
>             esac
>             xlib=`$echo "X$xlib" | $Xsed -e 's%^.*/%%'`
>             xdir="$gentop/$xlib"
2124a2133,2145
>             $show "${rm}r $xdir"
>             $run ${rm}r "$xdir"
>             $show "mkdir $xdir"
>             $run mkdir "$xdir"
>             status=$?
>             if test $status -ne 0 && test ! -d "$xdir"; then
>               exit $status
>             fi
>             $show "(cd $xdir && $AR x $xabs)"
>             $run eval "(cd \$xdir && $AR x \$xabs)" || exit $?
> 
>             libobjs="$libobjs "`find $xdir -name \*.o -print -o -name \*.lo -print | $NL2SP`
>           done
2235a2257,2264
>         for xlib in $convenience; do
>           # Extract the objects.
>           case "$xlib" in
>           [\\/]* | [A-Za-z]:[\\/]*) xabs="$xlib" ;;
>           *) xabs=`pwd`"/$xlib" ;;
>           esac
>           xlib=`$echo "X$xlib" | $Xsed -e 's%^.*/%%'`
>           xdir="$gentop/$xlib"
2236a2266,2278
>           $show "${rm}r $xdir"
>           $run ${rm}r "$xdir"
>           $show "mkdir $xdir"
>           $run mkdir "$xdir"
>           status=$?
>           if test $status -ne 0 && test ! -d "$xdir"; then
>             exit $status
>           fi
>           $show "(cd $xdir && $AR x $xabs)"
>           $run eval "(cd \$xdir && $AR x \$xabs)" || exit $?
> 
>           reload_conv_objs="$reload_objs "`find $xdir -name \*.o -print -o -name \*.lo -print | $NL2SP`
>         done

Re: [Mesa3d-users] mesa and quake3

[Joel F. <fus...@in...>]

I don't get the splash screen, but then again I don't even when I run
quake3 with the included mesa library and it works.  However, if I run a
program that uses libGL, I get a message saying "glide is compiled into
this library, but MESA_GLX_FX is not set".  Of course if I set it, I
don't get the error, but it doesn't seem to me that it's accelerated.  
In any case, it seems to me that this means that glide is at least "sort
of" compiled in, but for some reason libGL doesn't reference it at all
according to ldd, and of course quake3 gives the "unknown symbol:
grGlideInit" error.

I had already tried building it using the old Makefile.X11 system, but
it failed fairly early in the compile.  I don't remember the exact error
at this moment, but it was something about "no rule to make fxregoff.c"
in src/X86.  I'll try it again later and see exactly what it was.

I'll try posting on the newsgroups, but a few searches with deja didn't
turn up anything immediately...I'm thinking there just must be some
silly configuration problem here, but I can't figure out what.

Anyways, thanks for helping,

Joel

physic wrote:
> 
> Strange that it doesnt link to glide, yet you said earlier that the 3dfx
> splash screen is coming it.  I don't know what else to tell you.  You can
> trying building mesa with 'make -f Makefile.X11 linux-386-glide' or
> something like that.  Be sure to make clean first.  Also, check to make
> suere there arent other libGL.so files you are linking to.  And if all
> that fails try to contact some people that play quake3 under linux.  I
> suspect the vast majority of this list doesnt.
> 
> also read news://news.3dfx.com/3dfx.linux.apps.games
> also read news://news.3dfx.com/3dfx.glide.linux
> 
> On Fri, 24 Mar 2000, Joel Fuster wrote:
> 
> > Hmmm, it doesn't list libglide2x at all...I did the same to
> > libMesaVoodooGL and it lists glide2x and a few others that aren't listed
> > for libGL.so...  Am I not configuring with the right options?  I did:
> >
> > ./configure --with-glide=/usr --enable-3dnow=on
> >
> >
> > The glide libs are in /usr/lib, and the includes in /usr/include/glide.
> >
> > Looking at the top-level makefile after configuring, it seems that the
> > FX_LIB variables are set correctly... Any suggestions?
> >
> > Joel
> >
> >
> > physic wrote:
> > >
> > > Make sure the linker is actually finding glide.
> > >
> > >  ldd libGL.so
> > >
> > > should list the libraries it depends on and where it finds them.
> > >
> > > On Fri, 24 Mar 2000, Joel Fuster wrote:
> > >
> > > > I'm having a problem using the the CVS version of Mesa (as of 3/22/00)
> > > > with quake 3.  Configure says that it finds the glide.h and libglide2x,
> > > > and it seems to compile and install fine.  But when I start quake3, it
> > > > gives an error "Undefined symbol: grGlideInit" in libGL.so.  I should
> > > > note that the Mesa/demos work okay, and also that quake3 works fine with
> > > > the precompiled libMesaVoodooGL.so.3.2 that comes with quake3 1.16n.
> > > > I'm using glide 2.60, if that makes any difference.
> > >
> > > -physic
> >
> > _______________________________________________
> > Mesa3d-users mailing list
> > Mes...@li...
> > http://lists.sourceforge.net/mailman/listinfo/mesa3d-users
> >

[Mesa3d-users] DEC shared libraries

[Percy M. <pmo...@de...>]

Hi:

I am compiling Mesa 3.0 on my DEC machine with OSF 3.2 and it compiles
fine when I use the make osf1 option.

The problem is that when I statically link the libraries (libMesaGL.a,
libMesaGLU.a, libglut.a and libGLw.a) with my  applications, the
executable that I get has a link to the shared library libGLw.so in the
file.

I have rechecked my compiling options and compiled my code  with the
-non_shared option and some other options but I am still not able to get
rid of the shared
library linking and this causes a problem on some other DEC machines
(the code
will not run saying "shared library not found").

I have looked in the library files by searching for .so and the shared
library link
is not present. I am using Motif 1.2 and am pretty sure that I am not
doing any
funny stuff in my Makefile.

The temporary workaround is to copy the shared libraries from my
development machine to the other machines /usr/shlib.

Any comments/suggestions on how to go about actually getting rid of this

problem would be appreciated.

Thanks
Percy

Re: [Mesa3d-users] mesa and quake3

[physic <ph...@te...>]

Strange that it doesnt link to glide, yet you said earlier that the 3dfx
splash screen is coming it.  I don't know what else to tell you.  You can
trying building mesa with 'make -f Makefile.X11 linux-386-glide' or
something like that.  Be sure to make clean first.  Also, check to make
suere there arent other libGL.so files you are linking to.  And if all
that fails try to contact some people that play quake3 under linux.  I
suspect the vast majority of this list doesnt.

also read news://news.3dfx.com/3dfx.linux.apps.games
also read news://news.3dfx.com/3dfx.glide.linux

On Fri, 24 Mar 2000, Joel Fuster wrote:

> Hmmm, it doesn't list libglide2x at all...I did the same to
> libMesaVoodooGL and it lists glide2x and a few others that aren't listed
> for libGL.so...  Am I not configuring with the right options?  I did:
> 
> ./configure --with-glide=/usr --enable-3dnow=on
> 
> 
> The glide libs are in /usr/lib, and the includes in /usr/include/glide.
> 
> Looking at the top-level makefile after configuring, it seems that the
> FX_LIB variables are set correctly... Any suggestions?
> 
> Joel
> 
> 
> physic wrote:
> > 
> > Make sure the linker is actually finding glide.
> > 
> >  ldd libGL.so
> > 
> > should list the libraries it depends on and where it finds them.
> > 
> > On Fri, 24 Mar 2000, Joel Fuster wrote:
> > 
> > > I'm having a problem using the the CVS version of Mesa (as of 3/22/00)
> > > with quake 3.  Configure says that it finds the glide.h and libglide2x,
> > > and it seems to compile and install fine.  But when I start quake3, it
> > > gives an error "Undefined symbol: grGlideInit" in libGL.so.  I should
> > > note that the Mesa/demos work okay, and also that quake3 works fine with
> > > the precompiled libMesaVoodooGL.so.3.2 that comes with quake3 1.16n.
> > > I'm using glide 2.60, if that makes any difference.
> > 
> > -physic
> 
> _______________________________________________
> Mesa3d-users mailing list
> Mes...@li...
> http://lists.sourceforge.net/mailman/listinfo/mesa3d-users
> 

[Mesa3d-users] Sorry, newbie. How do I get this thing to work on Windows 98?

[James <fr...@we...>]

I've gone through all the documentation but I cant make heads or tails =
of it.

[Mesa3d-users] (no subject)

[Gerry C. <Ge...@fr...>]

 Hello as a new subscriber.

 I have a problem with widgets-sgi in Mesa version 3.1. I am using Motif
 Swim 2.0 commercial libraries and Mandrake Linux 6.1 with ATI 128 =
Xpert.


 Get following errors on linking:
 boilerplate.o: In function `main':
 boilerplate.o(.text+0x9fd): undefined reference to =
`GLwCreateMDrawingArea'
 /usr/X11R6/lib/libXm.so: undefined reference to `_xstat'
 collect2: ld returned 1 exit status

 mesa-widgets compiles OK and demos work fine but GLwCreateMDrawingArea
 does'nt get compiled - even with ./configure __with-motif.

I notice that GLwCreateMDrawingArea is declared as
an external in code. Where is this referenced to?

This all worked in Mesa-2.5 with Red Hat 3.1(I think)

 Can anyone help?

 Regards

 Gerry Cook

Re: [Mesa3d-users] Specific Questions about gl routines

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

sh...@pl... wrote:
> 
> Hello Folks,
>    I've just joined this forum. First off, Brian - congratulations to you and your collaborators on
> putting together a superb package.  Last weekend, a friend introduced me to msa3d and since then, my spare hours have almost exclusively been consumed with writing code using the mesa3d gl routines!

Glad you like it.


> In this context I'd like to know  if this forum is appropriate for posting specific questions about
> gl routines, or if its reserved for more general
> topics.
> 
> For instance, I have a question about glLightfv with
> the GL_SPOT_DIRECTION argument. But before I get into specifics, I'll wait for the response to my question above.


Generic OpenGL questions are probably best posted on the comp.graphics.api.opengl
usenet newsgroup.  Also, you might try reading the standard OpenGL
literature (books, specs, etc) as listed on www.opengl.org before posting
to a mailing list.  If all else fails, you can certainly ask here.

-Brian

[Mesa3d-users] Specific Questions about gl routines

[<sh...@pl...>]

Hello Folks,
   I've just joined this forum. First off, Brian - congratulations to you and your collaborators on 
putting together a superb package.  Last weekend, a friend introduced me to msa3d and since then, my spare hours have almost exclusively been consumed with writing code using the mesa3d gl routines!

In this context I'd like to know  if this forum is appropriate for posting specific questions about 
gl routines, or if its reserved for more general 
topics.

For instance, I have a question about glLightfv with 
the GL_SPOT_DIRECTION argument. But before I get into specifics, I'll wait for the response to my question above.

Thanks

-Sharat 
 

---------------------------------------------------
Get free personalized email at http://www.iname.com