[Please send followups to -ports, where this belongs.]

On Fri, Jun 23, 2000 at 04:06:55PM +0200, Norbert Irmer wrote:
> I tried to build the wxGTK-2.1.16 port, and noticed that
> a few AC_CHECK(..) macros in the configure script
> don't work.
> 
> The first header file which is not found is
> 
>   <X11/XKBlib.h>
> 
> because on FreeBSD systems there is no link 
> 
>   /usr/include/X11 -> /usr/X11R6/include
> 
> (shouldn't there be such a link ? - i heard this is a standard)

No, there should not be a link from /usr/include/X11 ->
/usr/X11R6/include.

However, I guess there is a bug in the configure script.  At that point
configure has already found the X11 include files, but then it doesn't
use them (see around line 1445 of `configure.in' for all of the
directories searched for X11 header files).  I'll fix when I get the
chance.

Hmm, wxGTK doesn't use this information anyway (no reference to
HAVE_X11_XKBLIB_H in the sources).

> The opengl header file <GL/gl.h> is also not found, and
> the link test with "libGL" or "libMesaGL" fails too.

It fails for the same reasons as the test for <X11/XKBlib.h>.

> And shouldn't there be a line in the Makefile of the port
> which shows how to compile wxGTK with opengl support ?
> (it took me an hour to find out how to do this!)  

I suppose it would be nice if there was a WANT_OPENGL knob.
I'll add one.

> So i would propose to make the following changes to the
> ports Makefile:
> 
> 
> CONFIGURE_ENV=        GTK_CONFIG="${X11BASE}/bin/gtk12-config"\
>                 CCFLAGS="-I/usr/X11R6/include"\
>               LDFLAGS="-L/usr/X11R6/lib"

That's a quickie fix.  I'll try to see what is wrong with the
configure script so we can send the fix back to the author.

> CONFIGURE_ARGS= "--with-opengl=yes"

One would have to include dependencies for Mesa as well, which
is why I'll wrap such with a WANT_OPENGL knob.

Thanks for your report,
-- 
Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to