Sign in to follow this  
pilgrim9684

Moving application from Windows to Linux

Recommended Posts

I have an application that I developed using Visual Studio 6.0 and 2005 to verify operation of framebuffer objects rendering to textures. However, now I need to port it to Linux and there is not glut or glew libraries or header files on the Linux system I need to port to. A search of the web does not yield glut binary files for Linux as are available for Windows; probably because of the differnt kernels out there. However, more disturbing is the absence of recent evidence of glut support for Linux. Have I missed something big here? What should I be using in the Linux world to replace the glut and glew functionality? Pilgrim

Share this post


Link to post
Share on other sites
For glut, use freeglut. GLEW works also on linux, to install the necessary headers, on a ubuntu system, install libglew-dev and freeglut3-dev , for other distros, the package names are similar.

Share this post


Link to post
Share on other sites
If you're looking for a glut replacement, I would recommend GLFW. It will require some changes to the code, but it'll probably be worth it in the end. Just take a look at its User Guide example and you'll see what I'm talking about. But if you'd rather stick with glut, I'm 100% sure there is a Linux version of it too, you just have to look around a bit. Or use FreeGlut like someone mentioned.

Share this post


Link to post
Share on other sites
All the packages mentioned are available for Linux. You just need to get used to the fact that getting them is actually *easier* on Linux, in some sense: Virtually all distributions have those libraries prepackaged, so you'll just have to go to your distribution's package manager and install them.

As has been pointed out before, most distributions split libraries into libfoo and libfoo-dev packages, where the former only contains the binaries and the latter contains the header files (and often pkg-config files) necessary to build programs.

Some distributions also have libfoo-dbg packages that contain debug versions of libraries, or debug symbols for the normal (non-debug) versions of libraries.

cu,
Prefect

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this