CYGWIN & Mesa GL Bloodshed Static Compile
Open Source C & C++ IDE for Windows
Brought to you by:
claplace
Menu
▾
▴
I hope you find this interesting.
I am trying to optimize a program I have worked on that I am porting from a Linux environment. I set up a Bloodshed C++ v4.1 environment parallel to a CYGWIN installation. I followed the instructions for using CYGWIN instead of Mingw and incoroporated Mesa GL. I converted. I compiled. I tested. Hey - it all works. But the perfectionist in me wants a static compile with a single executable. I want to dump the need for the Cygwin1.dll and the Glut32.dll (period) Now I know many who read this will say dump the Glut and the CYGWIN and be a real (OpenGL / C )programmer. Well - if I wanted all the heartache I would. I don't. Okay - so the question is how to get one executable using the wonderful Dev C IDE minus the need for those 2 pesky DLLs. (The astute will say - but hey what about the other OpenGL32 and GLU32 dlls - well I don't care about them [at this point] as I cannot make Windows users dump them and if they are there already when they buy Windows - so they can stay. Point Bill Gates team.) What I do care about is having people go through the trouble of downloading those extra files. (even if the Setup process of Dev C bundles them for delivery)
Anyhow - you can go to www.starshiptraders.com - click on sst software in the top left - go to windows binary - and see for yourself what I am talking about. Hey - play the game too if you want. I will offer that and free heckling as payment for reading my question and thinking of an answer. For the rest who can't help or arrive too late to answer the question first - take a break and play anyhow.
So - to repeat - how do I incorporate those dlls in a static compile? The compile line commands and options within the Dev C IDE environment would be nice. Just telling me to use the .a files with a .def file doesn't cut it. Oh and no - I don't want to compile within CYGWIN proper nor use a different compiler. I want the ease of the Bloodshed IDE and the power of CYGWIN and the flexibility of portable code.
Once I am done, I will be releasing the code under the GPL and other freedom type licensing for the client I am making.
Thanks for your time.
After much research, it appears the cygwin1.dll will always be required and that cygwin currently cannot be statically compiled.
One can hope.