From: "Matt D." <codespunk@gmail.com>
To: cygwin@cygwin.com
Subject: libglut is missing library for MinGW static linking
Date: Thu, 27 Sep 2018 13:42:00 -0000 [thread overview]
Message-ID: <34b0c5f5-1d4a-4ba6-c2ec-f0b105b590cb@gmail.com> (raw)
libglut-devel provides libglut.a and libglut.dll.a but linking libglut.a
with either "-lglut" or "-lglut.dll" both depend on either cygglut-3.dll
or libglut-0.dll respectively when compiling for Cygwin or MinGW.
I understand that this isn't a big deal for Cygwin binaries as it's not
possible to statically link those executables anyways. But glut has the
ability to link statically and this is of benefit on Windows with MinGW
for convenience and ease of distribution.
To perform static linking against glut, I have to download
"libfreeglut_static.a" as provided by http://freeglut.sourceforge.net. I
can still use libglut but the static library provides the missing
dependencies to mitigate the need for the shared library.
I can compile as such:
i686-w64-mingw32-g++.exe -DFREEGLUT_STATIC main.cpp -lglut
-lfreeglut_static -lgdi32 -lwinmm -lglu32 -lopengl32 -L. -oa.out
The resulting executable is completely static and stand-alone and does
not require a shared library. The key here is the define
"FREEGLUT_STATIC" along with libfreeglut_static provided from the
freeglut website.
I don't know what Cygwin's policy is on providing static libraries for
MinGW but this is a very good candidate as it already has all of the
necessary declarations defined.
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
next reply other threads:[~2018-09-27 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 13:42 Matt D. [this message]
2018-09-27 18:20 ` cyg Simple
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=34b0c5f5-1d4a-4ba6-c2ec-f0b105b590cb@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).