Difference between revisions of "Dependency Walker -- A remedy for distribution headaches"
From assela Pathirana
Jump to navigationJump to search
| Line 1: | Line 1: | ||
If you have ever tried to give away a reasonably complicated program that was written and compiled on windows to another user you should be very familiar with complaints of missing {{ | If you have ever tried to give away a reasonably complicated program that was written and compiled on windows to another user you should be very familiar with complaints of missing {{wikipedia|DLL}}s, and other dependencies and module mismatches etc., etc. These erros can manifest themselves in many forms (''The procedure entry point could not be located in the dynamic link library''; ''The application or DLL is not a valid Windows image'' or even ''Program too big to fit in memory''.) This is particularly so if you happen to be developing with a complex build environment that is tightly integrated with windows system, like visual studio (I often use Visual C++ 2005/2008 express (a.k.a. free) editions and they create a lot of trouble in deployment!) | ||
Revision as of 13:03, 29 January 2008
If you have ever tried to give away a reasonably complicated program that was written and compiled on windows to another user you should be very familiar with complaints of missing {{{2}}}s, and other dependencies and module mismatches etc., etc. These erros can manifest themselves in many forms (The procedure entry point could not be located in the dynamic link library; The application or DLL is not a valid Windows image or even Program too big to fit in memory.) This is particularly so if you happen to be developing with a complex build environment that is tightly integrated with windows system, like visual studio (I often use Visual C++ 2005/2008 express (a.k.a. free) editions and they create a lot of trouble in deployment!)
