To add the the compile error, strangely, after "Making all in lib" which is w/o notice or error, it starts "Making all in board3d" and the fist two commands succeed the second throwing a bunch of deprecated warnings (related to deprecated glu* functions). These produce libboard3d_la-drawboard3d.lo, libboard3d_la-drawboard3d.o and libboard3d_la-font3d.lo and it only fails following this, at the 4th command when compiling font3d.c into libboard3d_la-font3d.o.
I realise this may not run even if compiles, nevertheless it seems it DOES compile OpenGL with GLU up to some point before it fails which suggests GLU may be enough in itself to act as a binding to GL, or I just got it completely wrong. Regards, Marcel Fulop On Sun, Dec 10, 2017 at 5:18 PM, Marcell Fulop <[email protected]> wrote: > Hi Philippe, > > Thanks for the input. It seems you are right regarding the glew Homebrew > package. When installed and GLU_LIBS and GLU_CFLAGS are set, configure says > "checking for GLU... yes" and succeeds with --with-board3d. > > Trying with the OpenGL shipped with macOS High Siearra > (/System/Library/Frameworks/OpenGL.framework), and after fixing various > other dependencies, make fails after producing a bunch of errors like this: > > In file included from inc3d.h:44:0, > from font3d.c:25: > /System/Library/Frameworks/OpenGL.framework/Versions/A/Headers/glu.h:268:23: > note: declared here > extern GLUtesselator* gluNewTess (void) OPENGL_DEPRECATED(10_0, 10_9); > ^~~~~~~~~~ > font3d.c:543:64: error: invalid conversion from 'void (*)(GLenum, Mesh*) > {aka void (*)(unsigned int, _Mesh*)}' to 'GLvoid (*)() {aka void (*)()}' > [-fpermissive] > gluTessCallback(tobj, GLU_TESS_BEGIN_DATA, GLUFUN(tcbBegin)); > > I don't have any background in OpenGL just wandering what may be happening > here that the signature defined in glu.h (in macOS OpenGL) is different > from what is expected in gont3d.c? > > I realise it isn't going to work w/o some porting outlined in the linked > post... > > > > On Sat, Dec 9, 2017 at 9:05 AM, Philippe Michel <[email protected]> > wrote: > >> On Fri, Dec 08, 2017 at 06:13:00PM +1100, Marcell Fulop wrote: >> >> > I could only build w/o board3d, it gave me a weird error message about >> not >> > finding GTK when configuring with --with-board3d, but w/o it, it just >> > builds with GTK fine. Any clues to this one? >> > >> > $ ./configure --with-board3d >> > ... >> > checking for GTK... yes >> > checking for GTKGLEXT... yes >> > ... >> > checking GL/glx.h usability... no >> > checking GL/glx.h presence... no >> > checking for GL/glx.h... no >> > configure: error: board3d requested but gtk or gtkglext not found >> >> It looks like the build finds the gtk and gtkgkext libraries, but not >> those for glx (and the final error message is wrong and confusing). >> >> GLX is GL libraries for X but as far as I can read, MacOS High Sierra >> use Wayland (an aspiring replacement for X) for graphics. Probably the >> problem is there, for your build and for those trying to use the old >> binary packages as well. The article at >> http://www.tarnyko.net/en/?q=node/41 , for instance, summarize the >> issue. >> >> For your build, looking at the brew packages list (but I don't have a >> Mac to check), maybe installing the glew package would help. Or, looking >> at it from the other side, changing gnubg's 3d code to support GL >> natively on Wayland instead. >> >> For the old packages, maybe there is some optional compatibility layer, >> on merely some settings, available on High Sierra and needed to allow >> X applications to display on its Wayland server ? >> > >
_______________________________________________ Bug-gnubg mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-gnubg
