Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

with GNU build system #29

Open
josch opened this issue Sep 13, 2015 · 5 comments
Open

with GNU build system #29

josch opened this issue Sep 13, 2015 · 5 comments
Assignees

Comments

@josch
Copy link
Contributor

josch commented Sep 13, 2015

https://sourceforge.net/p/glui/patches/5/

original report

It has come to my attention again that some users desire an easier way to install and use GLUI.

A while back I had modified the build system of GLUI v2.2 to use autoconf, automake, and libtool. I neglected to post it to this tracker... sorry. I am posting it now in hopes that build system has not diverged much, and as such it will be useful.

I could probably be coerced into doing this for the current GLUI subversion revision.

... Nevermind, sourceforge has a file size limit. You can obtain the tarball at

https://artemis.sr.unh.edu/~tfogal/glui-2.2.tar.gz

reply 1

This is pretty important enhancement IMO. There are several parts of makefile that require hand-editing and tweaking that oculd be simplified and made more user-friendly and platform-portable. The autotools know which -g and -O flags are good on which platforms. There are easy ways to do flags to (for example) select among the various glut types, and check for their presence and location. As it becomes necessary to use different #include or other things on different platforms or versions of operating system, it's easy to detect and automatically compensate. Libtool would bring shared-library support and the idea of interface compatibility. And there would be an easy way to install the lib, rather than relying on manually copying files (which ones? where?).

@nigels-com
Copy link
Collaborator

I think the cmake build ought to suffice, personally.

@josch
Copy link
Contributor Author

josch commented Sep 24, 2015

Yes, probably. But as long as it works I plan to leave the original Makefile around.

I picked CMake instead of autotools because it supports generating Visual Studio projects for Windows.

But that CMakeLists.txt is still missing some targtets to generate the documentation for example. I'll close this bug once CMake support is complete.

@nigels-com
Copy link
Collaborator

I did give Windows a try, but I'm not sure what to do with freeglut for cmake to find it. Any suggestions?

@josch
Copy link
Contributor Author

josch commented Sep 24, 2015

On windows, the cmake variables GLUT_glut_LIBRARY and GLUT_INCLUDE_DIR have to be set manually in the cmake gui if either are not placed in the standard lookup paths (and they should probably not be put there in the first place).

@nigels-com
Copy link
Collaborator

Oh, that makes sense. Duh! :-)

@nigels-com nigels-com self-assigned this Jun 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants