I have gl libraries (Mesa3d) in non-standard places too.  To configure
properly I add the flags:
 --x-libraries=/path/to/Mesa.lib --libdir=/path/to/Mesa.lib
 when running the configure script.  This properly creates the
makefiles without any manual editing.

-Randy

On Mon, 21 Feb 2000, Jose Gomes wrote:

> Hello,
> 
> I have dx built, installed and running for linux and solaris
> and would like to report 3 problems. The fixes can be found
> in the file in attachment (which is the output of "cvs diff -C3").
> Please let me know if something is wrong with this.
> I hope this will help.
> 
> ii)
> 
> My opengl headers and libraries are not is a standard place.
> I added the options --with-gl-includes and --with-gl-libs
> to the "configure" script so that these locations can be passed
> to all Makefile.am through the variables GL_INCLUDES and GL_LIBS.
> See bellow for a list of modified files.
> 
> iii)
> 
> I have flex installed for solaris and the scripts think that
> linux implies flex and solaris implies lex.
> The problem is that flex and lex are not compatible.
> The file src/uipp/dxuilib/Network.C uses the "yylineno"
> variable which does not exists in flex but does in lex.
> This was taken into account in this C file by:
> #if defined(linux)  || defined(cygwin) || defined(freebsd)
> int yylineno;
> #else
> extern int yylineno;                    /* lexer line number      */
> #endif
> I think it is not the correct test since the fact "yylineno" exists
> is just a matter of "lex" or "flex".
> So, instead of adding the test "|| defined(solaris)",  I hadded the
> autoconf variable "HAVE_YYLINENO" (initialized by "configure")
> and replace the previous code by:
> #ifndef HAVE_YYLINENO
> int yylineno;
> #else
> extern int yylineno;                  /* lexer line number      */
> #endif
> See below for a list of modified files.
> 
> Non standard gl location.
> -------------------------
> 
> M configure.in
> M src/exec/dxexec/Makefile.am
> M src/exec/hwrender/Makefile.am
> M src/exec/hwrender/opengl/Makefile.am
> 

Reply via email to