You haven’t answered my questions so it is hard to help. Especially what compiler are you using?
If you use gcc then its easy since you just have to specify the library path to the folder where you saved your library. If you put it in c:\foo\bar then you would have
g++ -L/c/foo/bar main.o – but better than that with gcc tools you usually see the libraries in standard locations like /usr/local/lib and header in /usr/local/include. But you are not using gcc I suppose so this is for another audience that may see this post. I use dev-c++ in windows because it is gcc based.
If you are using a Microsoft specific compiler, you have to make sure you copy files to the correct library folder:
For Visual Studio 2008: (from link VS2008+GLUT)
glut32.lib to “Program Files\Microsoft Visual Studio 9.0\VC\lib”
glut.h to “Program Files\Microsoft Visual Studio 9.0\VC\include\GL”
For Visual Studio 2003 (from link Using Glut with Windows):
glut32.dll for Windows XP | Server 2003 to “C:\WINDOWS\system”
or for Windows 2000: to “C:\WINNT\system”
glut32.lib to “C:\Program Files\Microsoft Visual Studio NET 2003\Vc7\PlatformSDK\Lib”
glut.h to “C:\Program Files\Microsoft Visual Studio NET 2003\Vc7\PlatformSDK\Include\GL”
You get the point – you have to know what Microsoft compiler/what version/what year compiler you are using and put the *.lib, *.dll, *.h files in the “correct” places.
Notice how messy Microsoft is with its compilers – every new version changes where its standard libraries / headers are expected to be. You can get around that if you fiddle with the “link” menu options and set the library path… Anyhow I use linux/gcc or windows/dev-c++ tools to avoid all this microsoft crust. But that is beside the point. Any external libraries not a part of the OS will have to be treated this way – GLUT in Windows is no exception.