|
From: Earnie B. <ea...@us...> - 2012-08-11 16:21:04
|
On Fri, Aug 10, 2012 at 8:43 PM, mingw124 wrote: > > Alright, I've been trying this method. However the problems remains the same. > > What about when I have other dlls I want to link, what command and static > link name do I use? If you have the static library that matches the DLL then you simply do ``gcc -static -o MYPROG MYPROG.o -l MYLIBRARY'' > > I know exactly which dlls it requires but not how to link them statically so > I don't have to export them with the executable. If you don't have the static library that matches the DLL then you can't. The only difference would be adding -static to the link command but if you don't have the static library in the library search paths then you get dynamic library anyway. -- Earnie -- https://sites.google.com/site/earnieboyd |