plib-devel

RE: [Plib-devel] Q2: Water

[Dave M. <Dav...@dy...>]

in ssg.h i found

> virtual int getCareAbout ( int mode ) { return dont_care & (1<<mode) ; }

doesn't that seem negated?

also, there are a couple old hacks/hooks in the model loaders:

1) hookfunc
typedef ssgBranch *(*ssgHookFunc)(char *) ;
ssgEntity *ssgLoadXXX ( char *fname, ssgHookFunc hookfunc = NULL,
	ssgCreateFunc createfunc = NULL ) ;

2) _ssgGetAppState
ssgState *( *_ssgGetAppState)( char *) = NULL ;
void  ssgSetAppStateCallback ( ssgState *(*cb)(char *) ) ;

Are these hooks still used?  #1 is only implemented in ssgLoadAC::do_data
so it seems odd to have it passed to all loaders.  #2 could be easily
replaced with a leaf creation function.  Perhaps they could go away in
Plib 1.3 ??

--Dave McClurg

RE: [Plib-devel] User defined texture formats

[Dave M. <Dav...@dy...>]

Trent Gamblin wrote:
> I think SSG needs to have some hooks to allow user defined image 
> formats... 
 
I did a cvs commit which adds a leaf creation hook to ssgLoadAC.cxx
This should allow you to load the image formats you need.  This hook
should allow you to do other things like:
 
- load compressed or volumized textures
- strip off full paths from texture filenames
    i use that for ASE files because the modeler stores full paths
    whereas Steve likes a path that starts with '/' to be left alone.
- cull unwanted geometry or texture info
- recompute normals
 
Which format did you need?  I plan to get to the OBJ and ASE loaders
soon.
 
Look at the ssgIO.cxx module for how the default ssgCreateFunc hook
is written.
 
--Dave
 

Re: [Plib-devel] Q2: Water

[Sam S. <sa...@sp...>]

> 1) You can look down into the water and see the bottom just as clearly
>    as the sides. But once you are in the water, you can't see as far
>    as you could from above.  It's hard to fix that - but fortunately,
>    nobody seems to notice!

Couldn't you apply another "grey" texture on top on the water, with some
half decent alpha values?  Maybe the underwater caustic texture technique
would work on top of water as well
(http://reality.sgi.com/mjk/tips/caustics/)  You could also reflect some of
the surrounding objects in the water in a patchy fashion
(http://reality.sgi.com/opengl/tips/puddles/).

Should make the water look a lot less clear if you have the CPU/card usage
to go around :)

Sam

Re: [Plib-devel] User defined texture formats

[Steve B. <sjb...@ai...>]

> Dave McClurg wrote:

> When a leaf is created, the hook function can decide what it wants
> to do.  It could call it's own image loader for the texture.

<snip>

> I was going to wait until plib1.2 but I could commit now if
> Steve permits

Sure - I havn't had time to do much more in terms of releasing
a 1.2 version anyway.  Go for it!

I presume you can do this without breaking existing code though?
I wouldn't want to do that before 1.3.xx - and if possible, not
even then.

-- 
Steve Baker                  http://web2.airmail.net/sjbaker1
sjb...@ai... (home)  http://www.woodsoup.org/~sbaker
sj...@ht...      (work)

Re: [Plib-devel] Q2: Water

[Steve B. <sjb...@ai...>]

"Vallevand, Mark K" wrote:
> 
> Any suggestions for implementing water on a terrain using SSG?
> 
> Right now, I have water implemented as textured triangle strips on a
> 'sea-level' plain, and also adjust the fog when the camera is underwater.

Yep - that's more or less what I've done in Tux_AQFH - except that since
I had plenty of pixel fill to spare, I just made the water one *HUGE*
quadrilateral that runs under all of the terrain and only shows
through where the terrain drops below zero altitude.

It's not great for a couple of reasons:

1) You can look down into the water and see the bottom just as clearly
   as the sides. But once you are in the water, you can't see as far
   as you could from above.  It's hard to fix that - but fortunately,
   nobody seems to notice!

2) Very gently sloping 'beaches' tend to Z-fight with the water
   surface.  That would happen no matter what you did - but it's
   worse when the water runs under the ground.

> The terrain and water are just allowed to intersect each other without
> any adjustments, cutouts, etc.  This works pretty well except for some
> artifacting when viewed from a distance.  Flying along the terrain is
> rather nice.
> 
> But, there may be a better way to do this.

Bump-mapping looks really great on water - especially if you do
some texture animation tricks to make fake waves in the bump
map.

-- 
Steve Baker                  http://web2.airmail.net/sjbaker1
sjb...@ai... (home)  http://www.woodsoup.org/~sbaker
sj...@ht...      (work)

Re: [Plib-devel] Q1: Shared vertex data

[Steve B. <sjb...@ai...>]

"Vallevand, Mark K" wrote:

> > I don't have the SSG source code to quickly look at, but
> > I thought that ssgVtxTable used vertex arrays.  It seems
> > like a natural fit.

That's not an accident.

One of the reasons to go to the present ssgVtxTable from the
old ssgVTable was to make it easy to build a compatible
class that used CVA's (or just VA's) - so that is indeed the
next logical step.

> ssgVtxTable stores the vertex data in an array but passes it
> to OpenGL via glVertex
> 
>   glBegin ( gltype ) ;
>   for ( i = 0 ; i < num_vertices ; i++ )
>     glVertex3fv ( vx [ i ] ) ;
>   glEnd () ;
> 
> This is nice and straight-forward but not exactly optimal for large models.
> A seperate class, using vertex arrays, would be a useful addition to SSG.

Yep. 

> This might be worth looking at.  Hmm, Hmm.  You could use the
> existing SSG collection classes.  A class named ssgVtxArray, or
> some such thing.

Yes - that is exactly the plan...but in my present state of busy-ness,
I'm not going to be getting to do that very soon - so all contributions
are gratefully accepted.

-- 
Steve Baker                  http://web2.airmail.net/sjbaker1
sjb...@ai... (home)  http://www.woodsoup.org/~sbaker
sj...@ht...      (work)

RE: [Plib-devel] User defined texture formats

[Dave M. <Dav...@dy...>]

Here is the default leaf creation function.  I omitted
code to share textures and states for clarity but those
are just function calls.
 
ssgLeaf* _ssgCreateLeaf ( ssgCreateLeafData* data )
{
  ssgVtxTable *vtab = 0 ;
  if ( data )
  {
    vtab = new ssgVtxTable ( data->gltype,
      data->vl, data->nl, data->tl, data->cl ) ;
 
    ssgState *st = data -> st ;
    if ( st != NULL )
    {
      if ( data -> tfname != NULL )
      {
        ssgTexture* tex = new ssgTexture ( data -> tfname ) ;
        st -> setTexture ( tex ) ;
        st -> enable ( GL_TEXTURE_2D ) ;
      }
      else
        st -> disable ( GL_TEXTURE_2D ) ;
      vtab -> setState ( st ) ;
    }
  }
  return vtab ;
}

We should also allow the ssgTexture constructor to take a null arg
so we can load the texture in the application (png or jpeg) like
you requested.
 
--Dave

> I think SSG needs to have some hooks to allow user defined image 
> formats... Would this be useful to anyone else? 

Yes.  Very much.  I'm working on a hook for leaf creation during 
model load which is perhaps a more general case of what you want. 

When a leaf is created, the hook function can decide what it wants 
to do.  It could call it's own image loader for the texture. 

Other uses of a hook function during leaf creation include sharing 
ssgSimpleState entities, culling unwanted geometry, recomputing 
normals, and ignoring texture mapping coordinates/images. 

struct ssgCreateLeafData 
{ 
  char* parentName ; 
  GLenum gltype ; 
  ssgVertexArray *vl ; 
  ssgNormalArray *nl ; 
  ssgTexCoordArray *tl ; 
  ssgColourArray *cl ; 
  ssgSimpleState *st ;  //setTexture() not yet called 
  char* tfname ;                //nonzero if has texture 
} ; 

typedef ssgLeaf* (*ssgCreateLeafFunc)( ssgCreateLeafData* data ) ; 

I was going to wait until plib1.2 but I could commit now if 
Steve permits 

--Dave 

RE: [Plib-devel] User defined texture formats

[Dave M. <Dav...@dy...>]

> I think SSG needs to have some hooks to allow user defined image
> formats... Would this be useful to anyone else?

Yes.  Very much.  I'm working on a hook for leaf creation during
model load which is perhaps a more general case of what you want.

When a leaf is created, the hook function can decide what it wants
to do.  It could call it's own image loader for the texture.

Other uses of a hook function during leaf creation include sharing
ssgSimpleState entities, culling unwanted geometry, recomputing
normals, and ignoring texture mapping coordinates/images.

struct ssgCreateLeafData
{
  char* parentName ;
  GLenum gltype ;
  ssgVertexArray *vl ;
  ssgNormalArray *nl ;
  ssgTexCoordArray *tl ;
  ssgColourArray *cl ;
  ssgSimpleState *st ;	//setTexture() not yet called
  char* tfname ;		//nonzero if has texture
} ;

typedef ssgLeaf* (*ssgCreateLeafFunc)( ssgCreateLeafData* data ) ;

I was going to wait until plib1.2 but I could commit now if
Steve permits

--Dave

[Plib-devel] User defined texture formats

[Trent G. <tm...@cy...>]

I think SSG needs to have some hooks to allow user defined image
formats, or support more formats natively. Native support for complex
formats like JPEG or PNG can only be done by duplicating a lot of
code, since Steve doesn't want any extra library dependencies.

Would this be useful to anyone else? Does anyone have any ideas on how
we could allow user defined image formats? I'm a C programmer, so the
first thing I think of is an array of function pointers and a function
to register new formats, something like:

int register(char *ext, void (*func)(char *fname, char **data, int *w,
  int *h, int *z)

Then have ssgImageLoader::loadTexture look for a user function if an
internal one doesn't exist. But maybe there is a better way in C++?

The reason I need this is so I can call functions like ssgLoadAC,
where the models have textures in them in formats that aren't
supported by SSG. Converting my textures to BMP or SGI is not really
an option, because they go from about 5 megs (jpg) to over 60 megs.

RE: [Plib-devel] Q1: Shared vertex data

[Vallevand, M. K <Mar...@UN...>]

-----Original Message-----
From: Dave McClurg [mailto:Dav...@dy...]
Sent: Monday, May 08, 2000 12:03 PM
To: 'pli...@li...'
Subject: RE: [Plib-devel] Q1: Shared vertex data



> When I looked at vertex arrays, it was not clear to me how 
> they could even be used to share vertex data, which is my 
> aim. 
> 
http://www.sgi.com/software/opengl/examples/redbook/source/varray.c
<http://www.sgi.com/software/opengl/examples/redbook/source/varray.c>   

 

DOH!

I get it now... 

> I don't have the SSG source code to quickly look at, but 
> I thought that ssgVtxTable used vertex arrays.  It seems 
> like a natural fit. 
> 
ssgVtxTable stores the vertex data in an array but passes it 
to OpenGL via glVertex 

  glBegin ( gltype ) ; 
  for ( i = 0 ; i < num_vertices ; i++ ) 
    glVertex3fv ( vx [ i ] ) ; 
  glEnd () ; 

This is nice and straight-forward but not exactly optimal for large models. 
A seperate class, using vertex arrays, would be a useful addition to SSG.  

 

This might be worth looking at.  Hmm, Hmm.  You could use the 

existing SSG collection classes.  A class named ssgVtxArray, or

some such thing.  Hmm.  Let me play with the idea for a while.

--Dave  


 
 

Regards. 
Mark K Vallevand   ma...@rs... 
Outside of a dog, a book is man's best friend. 
 Inside of a dog, its too dark to read.  - Groucho 

 

 

RE: [Plib-devel] Q1: Shared vertex data

[Dave M. <Dav...@dy...>]

> When I looked at vertex arrays, it was not clear to me how
> they could even be used to share vertex data, which is my
> aim.
>
http://www.sgi.com/software/opengl/examples/redbook/source/varray.c

> I don't have the SSG source code to quickly look at, but
> I thought that ssgVtxTable used vertex arrays.  It seems
> like a natural fit.
>
ssgVtxTable stores the vertex data in an array but passes it
to OpenGL via glVertex

  glBegin ( gltype ) ;
  for ( i = 0 ; i < num_vertices ; i++ )
    glVertex3fv ( vx [ i ] ) ;
  glEnd () ;

This is nice and straight-forward but not exactly optimal for large models.
A seperate class, using vertex arrays, would be a useful addition to SSG.

--Dave

RE: [Plib-devel] Q1: Shared vertex data

[Vallevand, M. K <Mar...@UN...>]

When I looked at vertex arrays, it was not clear to me how
they could even be used to share vertex data, which is my
aim.
 
I don't have the SSG source code to quickly look at, but
I thought that ssgVtxTable used vertex arrays.  It seems
like a natural fit.
 

Regards. 
Mark K Vallevand   ma...@rs... 
Outside of a dog, a book is man's best friend. 
 Inside of a dog, its too dark to read.  - Groucho 

 

-----Original Message-----
From: Dave McClurg [mailto:Dav...@dy...]
Sent: Monday, May 08, 2000 11:36 AM
To: 'pli...@li...'
Subject: RE: [Plib-devel] Q1: Shared vertex data



> Is there a way with SSG to share vertex data between the triangles, 
> triangle fans, triangle strips, etc that are defined using 
> ssgVtxTable? 
> 
Nope.  Currently, SSG does not support vertex arrays. 
That would be a very useful class to add.  Care to write it? 

RE: [Plib-devel] Q1: Shared vertex data

[Dave M. <Dav...@dy...>]

> Is there a way with SSG to share vertex data between the triangles,
> triangle fans, triangle strips, etc that are defined using 
> ssgVtxTable?
> 
Nope.  Currently, SSG does not support vertex arrays.
That would be a very useful class to add.  Care to write it?

[Plib-devel] Q2: Water

[Vallevand, M. K <Mar...@UN...>]

Any suggestions for implementing water on a terrain using SSG?

Right now, I have water implemented as textured triangle strips on a
'sea-level' plain, and also adjust the fog when the camera is underwater.
The terrain and water are just allowed to intersect each other without
any adjustments, cutouts, etc.  This works pretty well except for some
artifacting when viewed from a distance.  Flying along the terrain is
rather nice.

But, there may be a better way to do this.

Regards.
Mark K Vallevand   ma...@rs...
Outside of a dog, a book is man's best friend.
 Inside of a dog, its too dark to read.  - Groucho

[Plib-devel] Q1: Shared vertex data

[Vallevand, M. K <Mar...@UN...>]

Is there a way with SSG to share vertex data between the triangles,
triangle fans, triangle strips, etc that are defined using ssgVtxTable?

Right now, I reconstruct the ssgVtxTable objects that are affected 
when I dynamically adjust the terrain in my program.

But, there may be a better way to do this.

Regards.
Mark K Vallevand   ma...@rs...
Outside of a dog, a book is man's best friend.
 Inside of a dog, its too dark to read.  - Groucho

[Plib-devel] Great! Thank you, Bram Stolk&Steve Baker

[Wein G. <cr...@us...>]

 
> > checking for gcc... (cached) cc
> > checking whether the C compiler (cc -Wall ) works... no
> > configure: error: installation or configuration problem: C compiler
cannot
> > create executables.
> > $
> > 
> > Any further suggestion? Thanks again.
> 
> remove config.cache and try again.
> 
> config.cache should always be removed if you have changed
> the CC, CXX, CFLAGS or CXXFLAGS environment vars.
 
Great! No compile problems in my SGI system. I can use either SGI
C++ compiler or Gnu gcc/g++ compiler.  Sounds PLIB is a more
reliable software. Thank you again!

By the way, I hope to learn some detail things about config.cache,
variable setting, etc. Where can I find some web sites to explain 
these? I already knew one:  http://www.gnu.org/manual/manual.html
Anything else? 

Best regards,

-Wein



____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1

Re: [Plib-devel] No errors in SGI C++ compiling, many thanks. But...

[Bram S. <br...@ch...>]

Wein Gui wrote:

> checking for gcc... (cached) cc
> checking whether the C compiler (cc -Wall ) works... no
> configure: error: installation or configuration problem: C compiler cannot
> create executables.
> $
> 
> Any further suggestion? Thanks again.

remove config.cache and try again.

config.cache should always be removed if you have changed
the CC, CXX, CFLAGS or CXXFLAGS environment vars.


-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
  Bram Stolk               "Linux - Why use windows, if there is a door?"
  work: br...@sa...
  priv: br...@ch...

[Plib-devel] No errors in SGI C++ compiling, many thanks. But...

[Wein G. <cr...@us...>]

>>   When using SGI c/c++ compiler 7.3 to compile plib and FlightGear`s
>>   code, I met many errors, and couldn`t continue compiling it.
>
> I have compiled PLIB under SGI`s C++ compiler (dunno if it was v7.3 or
> not though).  Could you tell me what the errors were - I`d like for it
> to compile under SGI`s compiler.

After I modified some codes according to you last answer, plib can be
compiled without errors in my SGI Irix 6.5.7 with SGI C++ compiler. 
Thank you so much.

Because of some errors in compiling FlightGear in SGI C++, I need to
re-compile both plib and FlightGear in GNU gcc/g++. 
           
>>   Therefore, I must change to GNU platform. But, I don`t know how to
>>   change autoconf(configure.in, etc.) to my case, i.e. to use gcc/g++
>>   instead of former cc/CC of original SGI compiler. By the way,
>>   I already installed a gcc-2.95.2 Compiler Suite.
>  
>           For GNU, you could do:
>
>           export CC=gcc
>           export CXX=g++
>           export CFLAGS=-Wall
>           export CXXFLAGS=-Wall
>           ./configure

Some errors appears after I followed this way:

1% sh
$ export CC=gcc
$ export CXX=g++
$ export CFLAGS=-Wall
$ export CXXFLAGS=-Wall
$ ./configure
loading cache ./config.cache
checking for a BSD compatible install... ./install-sh -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... missing
includedir changed to ${prefix}/include/plib libdir is ${exec_prefix}/lib
checking for gcc... (cached) cc
checking whether the C compiler (cc -Wall ) works... no
configure: error: installation or configuration problem: C compiler cannot
create executables.
$ 

Any further suggestion? Thanks again.


-Wein

____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1

Re: [Plib-devel] How to change to gcc/g++ instead of cc/CC of SGI compiler?

[Bram S. <br...@ch...>]

Wein Gui wrote:
> 
>   Hello,
> 
>   When using SGI c/c++ compiler 7.3 to compile plib and FlightGear's
>   code, I met many errors, and couldn't continue compiling it.
>   Therefore, I must change to GNU platform. But, I don't know how to
>   change autoconf(configure.in, etc.) to my case, i.e. to use gcc/g++
>   instead of former cc/CC of original SGI compiler. By the way,
>   I already installed a gcc-2.95.2 Compiler Suite.

Use:

export CC=cc
export CXX=CC
export CFLAGS=-mips2
export CXXFLAGS=-mips3
./configure 

...if you want sgi's compiler.

For GNU, you could do:

export CC=gcc
export CXX=g++
export CFLAGS=-Wall
export CXXFLAGS=-Wall
./configure

e.g.

   Bram


> 
>   Thank you so much.
> 
>   -Wein
> 
> ____________________________________________________________________
> Get free email and a permanent address at http://www.netaddress.com/?N=1
> 
> _______________________________________________
> plib-devel mailing list
> pli...@li...
> http://lists.sourceforge.net/mailman/listinfo/plib-devel

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
  Bram Stolk               "Linux - Why use windows, if there is a door?"
  work: br...@sa...
  priv: br...@ch...

Re: [Plib-devel] How to change to gcc/g++ instead of cc/CC of SGI compiler?

[Steve B. <sjb...@ai...>]

Wein Gui wrote:

>   When using SGI c/c++ compiler 7.3 to compile plib and FlightGear's
>   code, I met many errors, and couldn't continue compiling it.

I have compiled PLIB under SGI's C++ compiler (dunno if it was v7.3 or
not though).  Could you tell me what the errors were - I'd like for it
to compile under SGI's compiler.
 
>   Therefore, I must change to GNU platform. But, I don't know how to
>   change autoconf(configure.in, etc.) to my case, i.e. to use gcc/g++
>   instead of former cc/CC of original SGI compiler. By the way,
>   I already installed a gcc-2.95.2 Compiler Suite.

Hmmm - I don't know either.  That's one of those black magic things
that autoconf 'just does'.

There is probably a command-line option to the ./configure script.
Check the 'INSTALL' file in the PLIB distro.


-- 
Steve Baker                  http://web2.airmail.net/sjbaker1
sjb...@ai... (home)  http://www.woodsoup.org/~sbaker
sj...@ht...      (work)

[Plib-devel] How to change to gcc/g++ instead of cc/CC of SGI compiler?

[Wein G. <cr...@us...>]

  Hello,
 
  When using SGI c/c++ compiler 7.3 to compile plib and FlightGear's
  code, I met many errors, and couldn't continue compiling it. 
  Therefore, I must change to GNU platform. But, I don't know how to
  change autoconf(configure.in, etc.) to my case, i.e. to use gcc/g++ 
  instead of former cc/CC of original SGI compiler. By the way,
  I already installed a gcc-2.95.2 Compiler Suite.

  Thank you so much.

  -Wein

____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1

Re: [Plib-devel] Compiling problems in SGI Irix 6.5.7

[Steve B. <sjb...@ai...>]

Wein Gui wrote:
> 
> Hi, friends,
> 
> I am trying my first compilation of Plib for FlightGear, and use SGI
> Octane machine's 7.3 C++ compiler in IRIX 6.5.7.
> 
> I have installed all the needed libraries without any problems and
> configure is happy. But now when I tried to "make", it stops on an
> error:

> cc-1020 CC: ERROR File = sgIsect.cxx, Line = 29
>   The identifier "FLT_EPSILON" is undefined.
> 
>     if ( dnorm < FLT_EPSILON )
>                  ^

This has obviously been a problem before - because in sg.cxx (where
FLT_EPSILON has also been used), it says:

  #ifndef FLT_EPSILON
  #define FLT_EPSILON 1.19209290e-07f        
  #endif

...I should probably copy those three lines into the top of
sgIsect.cxx

> cc-1133 CC: ERROR File = ssgSimpleState.cxx, Line = 18
>   Expression must be a modifiable lvalue.
> 
>     specular_colour = src -> specular_colour ;
>     ^
> 
> cc-1133 CC: ERROR File = ssgSimpleState.cxx, Line = 19
>   Expression must be a modifiable lvalue.

These are actually fixed in the latest CVS version - I havn't had
the time to make a proper release out of it though.

Change those four lines to:

  sgCopyVec4 ( specular_colour, src -> specular_colour ) ;
  sgCopyVec4 ( emission_colour, src -> emission_colour ) ;
  sgCopyVec4 (  ambient_colour, src ->  ambient_colour ) ;
  sgCopyVec4 (  diffuse_colour, src ->  diffuse_colour ) ;                      

...and all will be well.

--
Steve Baker                  http://web2.airmail.net/sjbaker1
sjb...@ai... (home)  http://www.woodsoup.org/~sbaker
sj...@ht...      (work)

Re: [Plib-devel] Compiling problems in SGI Irix 6.5.7

[Curtis L. O. <cu...@me...>]

Wein,

You might try 'grep'ing through your /usr/include directory for this
missing identifyer.  It could be that for irix, you need an additional
#include.

Regards,

Curt.

Wein Gui writes:
>   Hi, friends,
> 
>   I am trying my first compilation of Plib for FlightGear, and use SGI
>   Octane machine's 7.3 C++ compiler in IRIX 6.5.7.
> 
>   I have installed all the needed libraries without any problems and
>   configure is happy. But now when I tried to "make", it stops on an 
>   error:
> 
>   --------------------------Error 1-------------------------- 
>   CC -DPACKAGE=\"plib\" -DVERSION=\"1.1.11\" -DHAVE_LIBGLCORE=1
>   -DHAVE_LIBGL=1 -DHAVE_LIBGLU=1 -DHAVE_LIBGLUT
>   =1 -DHAVE_LIBAUDIO=1 -DSTDC_HEADERS=1 -DHAVE_GL_GL_H=1 -DHAVE_GL_GLU_H=1
>   -DGLUT_IS_PRESENT=1 -I. -I. -g -I/usr/local/include
>   -L/usr/local/lib -c sgIsect.cxx
>   cc-1020 CC: ERROR File = sgIsect.cxx, Line = 29
>   The identifier "FLT_EPSILON" is undefined.
> 
>   if ( dnorm < FLT_EPSILON )
>   ^
> 
>   cc-1020 CC: ERROR File = sgIsect.cxx, Line = 89
>   The identifier "FLT_EPSILON" is undefined.
> 
>   if ( sgAbs ( tmp ) < FLT_EPSILON )
>   ^
> 
>   cc-1020 CC: ERROR File = sgIsect.cxx, Line = 127
>   The identifier "FLT_EPSILON" is undefined.
> 
>   if ( dist < FLT_EPSILON )
>   ^
>   3 errors detected in the compilation of "sgIsect.cxx".
>   *** Error code 2 (bu21)
>   *** Error code 1 (bu21)
>   *** Error code 1 (bu21)
>   -------------------Error 1 end-----------------------
> 
> 
> 
> 
>   I define the FLT_EPSILON to a value randomly, say, 1.0, 
>   it continues "make" and stops at another big error:
> 
>   -------------------Error 2 begin-----------------
> 
> 
>   cc-1133 CC: ERROR File = ssgSimpleState.cxx, Line = 18
>   Expression must be a modifiable lvalue.
> 
>   specular_colour = src -> specular_colour ;
>   ^
> 
>   cc-1133 CC: ERROR File = ssgSimpleState.cxx, Line = 19
>   Expression must be a modifiable lvalue.
> 
>   emission_colour = src -> emission_colour ;
>   ^
> 
>   cc-1133 CC: ERROR File = ssgSimpleState.cxx, Line = 20
>   Expression must be a modifiable lvalue.
> 
>   ambient_colour = src -> ambient_colour ;
>   ^
> 
>   cc-1133 CC: ERROR File = ssgSimpleState.cxx, Line = 21
>   Expression must be a modifiable lvalue.
> 
>   diffuse_colour = src -> diffuse_colour ;
>   ^
> 
>   4 errors detected in the compilation of "ssgSimpleState.cxx".
>   *** Error code 2 (bu21)
>   *** Error code 1 (bu21)
>   *** Error code 1 (bu21)
> 
>   ------------------------------------
> 
> 
>   How to solve these problems? Would you please kindly enough
>   to help me to finish "make" in SGI environment?
> 
>   Many thanks.
> 
>   -Wein
> 
> 
> ____________________________________________________________________
> Get free email and a permanent address at http://www.netaddress.com/?N=1
> 
> _______________________________________________
> plib-devel mailing list
> pli...@li...
> http://lists.sourceforge.net/mailman/listinfo/plib-devel

-- 
Curtis Olson   Human Factors Research Lab       Flight Gear Project
Twin Cities    cu...@hf...                cu...@fl...
Minnesota      http://www.menet.umn.edu/~curt   http://www.flightgear.org

[Plib-devel] Compiling problems in SGI Irix 6.5.7

[Wein G. <cr...@us...>]

 
  Hi, friends,

  I am trying my first compilation of Plib for FlightGear, and use SGI
  Octane machine's 7.3 C++ compiler in IRIX 6.5.7.

  I have installed all the needed libraries without any problems and
  configure is happy. But now when I tried to "make", it stops on an 
  error:

  --------------------------Error 1-------------------------- 
  CC -DPACKAGE=\"plib\" -DVERSION=\"1.1.11\" -DHAVE_LIBGLCORE=1
  -DHAVE_LIBGL=1 -DHAVE_LIBGLU=1 -DHAVE_LIBGLUT
  =1 -DHAVE_LIBAUDIO=1 -DSTDC_HEADERS=1 -DHAVE_GL_GL_H=1 -DHAVE_GL_GLU_H=1
  -DGLUT_IS_PRESENT=1 -I. -I. -g -I/usr/local/include
  -L/usr/local/lib -c sgIsect.cxx
  cc-1020 CC: ERROR File = sgIsect.cxx, Line = 29
  The identifier "FLT_EPSILON" is undefined.

  if ( dnorm < FLT_EPSILON )
  ^

  cc-1020 CC: ERROR File = sgIsect.cxx, Line = 89
  The identifier "FLT_EPSILON" is undefined.

  if ( sgAbs ( tmp ) < FLT_EPSILON )
  ^

  cc-1020 CC: ERROR File = sgIsect.cxx, Line = 127
  The identifier "FLT_EPSILON" is undefined.

  if ( dist < FLT_EPSILON )
  ^
  3 errors detected in the compilation of "sgIsect.cxx".
  *** Error code 2 (bu21)
  *** Error code 1 (bu21)
  *** Error code 1 (bu21)
  -------------------Error 1 end-----------------------




  I define the FLT_EPSILON to a value randomly, say, 1.0, 
  it continues "make" and stops at another big error:

  -------------------Error 2 begin-----------------


  cc-1133 CC: ERROR File = ssgSimpleState.cxx, Line = 18
  Expression must be a modifiable lvalue.

  specular_colour = src -> specular_colour ;
  ^

  cc-1133 CC: ERROR File = ssgSimpleState.cxx, Line = 19
  Expression must be a modifiable lvalue.

  emission_colour = src -> emission_colour ;
  ^

  cc-1133 CC: ERROR File = ssgSimpleState.cxx, Line = 20
  Expression must be a modifiable lvalue.

  ambient_colour = src -> ambient_colour ;
  ^

  cc-1133 CC: ERROR File = ssgSimpleState.cxx, Line = 21
  Expression must be a modifiable lvalue.

  diffuse_colour = src -> diffuse_colour ;
  ^

  4 errors detected in the compilation of "ssgSimpleState.cxx".
  *** Error code 2 (bu21)
  *** Error code 1 (bu21)
  *** Error code 1 (bu21)

  ------------------------------------


  How to solve these problems? Would you please kindly enough
  to help me to finish "make" in SGI environment?

  Many thanks.

  -Wein


____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1

[Plib-devel] Compiling problems in SGI Irix 6.5.7

[Wein G. <cr...@us...>]

Hi, friends,

I am trying my first compilation of Plib for FlightGear, and use SGI
Octane machine's 7.3 C++ compiler in IRIX 6.5.7.

I have installed all the needed libraries without any problems and
configure is happy. But now when I tried to "make", it stops on an 
error:

--------------------------Error 1-------------------------- 
 CC -DPACKAGE=\"plib\" -DVERSION=\"1.1.11\" -DHAVE_LIBGLCORE=1
 -DHAVE_LIBGL=1 -DHAVE_LIBGLU=1 -DHAVE_LIBGLUT
=1 -DHAVE_LIBAUDIO=1 -DSTDC_HEADERS=1 -DHAVE_GL_GL_H=1 -DHAVE_GL_GLU_H=1
  -DGLUT_IS_PRESENT=1  -I. -I.      -g -I/usr/local/include
  -L/usr/local/lib -c sgIsect.cxx
cc-1020 CC: ERROR File = sgIsect.cxx, Line = 29
  The identifier "FLT_EPSILON" is undefined.

    if ( dnorm < FLT_EPSILON )
                 ^

cc-1020 CC: ERROR File = sgIsect.cxx, Line = 89
  The identifier "FLT_EPSILON" is undefined.

    if ( sgAbs ( tmp ) < FLT_EPSILON )
                         ^

cc-1020 CC: ERROR File = sgIsect.cxx, Line = 127
  The identifier "FLT_EPSILON" is undefined.

    if ( dist < FLT_EPSILON )
                ^
3 errors detected in the compilation of "sgIsect.cxx".
*** Error code 2 (bu21)
*** Error code 1 (bu21)
*** Error code 1 (bu21)
-------------------Error 1 end-----------------------



 
I define the FLT_EPSILON to a value randomly, say, 1.0, 
it continues "make" and stops at another big error:

-------------------Error 2 begin-----------------
              

cc-1133 CC: ERROR File = ssgSimpleState.cxx, Line = 18
  Expression must be a modifiable lvalue.

    specular_colour = src -> specular_colour ;
    ^

cc-1133 CC: ERROR File = ssgSimpleState.cxx, Line = 19
  Expression must be a modifiable lvalue.

    emission_colour = src -> emission_colour ;
    ^

cc-1133 CC: ERROR File = ssgSimpleState.cxx, Line = 20
  Expression must be a modifiable lvalue.

     ambient_colour = src ->  ambient_colour ;
     ^

cc-1133 CC: ERROR File = ssgSimpleState.cxx, Line = 21
  Expression must be a modifiable lvalue.

     diffuse_colour = src ->  diffuse_colour ;
     ^

4 errors detected in the compilation of "ssgSimpleState.cxx".
*** Error code 2 (bu21)
*** Error code 1 (bu21)
*** Error code 1 (bu21)
 
------------------------------------


How to solve these problems? Would you please kindly enough
to help me to finish "make" in SGI environment?

Many thanks.

-Wein

____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1