public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Matt D." <codespunk@gmail.com>
To: cygwin@cygwin.com
Subject: What is the purpose of libglut32?
Date: Thu, 27 Sep 2018 12:50:00 -0000	[thread overview]
Message-ID: <dcc6471d-f995-52b8-2770-1f523ae34ae6@gmail.com> (raw)

Does anyone know what libglut32 is used for? It comes as part of 
"w32api-runtime" and "mingw64-i686-runtime" and is installed into:

usr/lib/w32api/libglut32.a

and

usr/i686-w64-mingw32/sys-root/mingw/lib/libglut32.a

I haven't been able to find a use for this as attempting to link with it 
produces the following errors:

undefined reference to `_imp____glutInitWithExit@12'
undefined reference to `_imp____glutCreateWindowWithExit@8'
undefined reference to `_imp____glutCreateMenuWithExit@8'

It is possible to link with it if -DGLUT_DISABLE_ATEXIT_HACK is used to 
skip these declarations but then it depends upon glut32.dll which isn't 
provided by any package. How can libglut32 be used for anything if it is 
missing its binary dependency? Is this library unused? Is the glut32.dll 
dependency an error?

Also note that this define really isn't meant to be used since it 
disables a necessary workaround as defined in freeglut_std.h.

See here:

 > Win32 has an annoying issue where there are multiple C run-time
 > libraries (CRTs). If the executable is linked with a different CRT
 > from the GLUT DLL, the GLUT DLL will not share the same CRT static
 > data seen by the executable. In particular, atexit callbacks
 > registered in the executable will not be called if GLUT calls its
 > (different) exit routine. GLUT is typically built with the
 > "/MD" option (the CRT with multithreading DLL support), but the Visual
 > C++ linker default is "/ML" (the single threaded CRT).
 >
 > One workaround to this issue is requiring users to always link with
 > the same CRT as GLUT is compiled with. That requires users supply a
 > non-standard option. GLUT 3.7 has its own built-in workaround where
 > the executable's "exit" function pointer is covertly passed to GLUT.
 > GLUT then calls the executable's exit function pointer to ensure that
 > any "atexit" calls registered by the application are called if GLUT
 > needs to exit.
 >
 > Note that the __glut*WithExit routines should NEVER be called
 > directly. To avoid the atexit workaround, #define
 > GLUT_DISABLE_ATEXIT_HACK.

This library is NOT the same as libgut, which seems to be the 
appropriate way to include glut, even when compiling for MinGW.


Matt D.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2018-09-27 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27 12:50 Matt D. [this message]
2018-09-27 13:43 ` Jon Turney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dcc6471d-f995-52b8-2770-1f523ae34ae6@gmail.com \
    --to=codespunk@gmail.com \
    --cc=codespunk+cygwin@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).