If only lib1.dll uses functions exported by lib2.dll, you do not need to
link with lib2.dll. If your main program does use functions exported by
lib2.dll, why should you expect you can dispense with the linking
procedure? Sorry but it is not the way DLL works.
Programming is mostly to adapt people's brains to work like machines, not
vice versa. If you want to do something in the opposite way, maybe you
should design a new language. Of course, implementing the language is
"Christophe & Nadine Enderlin" <christophe.enderlin@...>
Subject: [Mingw-users] Dll against Dll
I've got a problem with building dll.
When a dll (lib1.dll) is linked against a second one (lib2.dll), it
exports its own functions, but not the ones it imported from lib2.dll
So, if I build an executable linked against lib1.dll, and if this
executable needs a function provided by lib2.dll, it won't find it. So, to
solve this problem, I must explicitly link my executable with both
lib1.dll and lib2.dll
Is there a way to make this work with linking my executable only
Thanks for your answers!
Get latest updates about Open Source Projects, Conferences and News.