I need to make a correction to my previous statement...

Static declarations are detected in Dependency Walker when you drag yourExecutable.exe and place it in the Dependency Walker's main window. However, what I learned yesterday is that Dependency walker will find dynamic dependencies also.

Dynamic dependencies are found by running a Static detection and then using the "Profile" pulldown menu and selecting "Start Profiling".

This will show you everytime that your executable called upon qtcore4.dll AND what qtcore4 called, that is how I confirmed that I also needed to add the qico4.dll as well as the qjpeg4.dll to my VS setup project. This will actually execute your app in the process. It is a very cool feature of Dependency Walker of which I was unaware.

Anyway, because I did not know that I could use Dependency Walker to find Dynamic Dependencies; I incorrectly stated that I did not know what dependencies I was missing. I hope this helps.

This forum, or more accurately the Members of this forum have been very helpful!

Thanks;
masher
PS: If your app is 32bit then you must use the 32bit version of Dependency Walker, or 64bit for a 64bit app. The Dynamic feature will not work otherwise.