I thought if you compile a Visual-studio 2013 Win32 project using `/MT` Code Generation->Runtime library then it will automatically package all dependency dll's - including 3rd party dll's - into the executable?

Currently certain users get an error when running my .exe. Its related to not having a 3rd party dll (OpenSSL):

The program can't start because LIBEAY32.dll is missing from your computer

This error has occurred for users using my .exe on Windows 10 OS's. How can I ensure all dependency dll's are packaged into my .exe?

I currently compile my application on my 64bit Windows 8.1 OS. The win32 visual-studio project is compiled using the following project properties:

• Character Set: Unicode char set
• Use of MFC: Use standard windows libraries
• Whole Program Optimisation: Use Link Time Code Generation
• Debug info format: none
• Code Generation->Runtime library: /MT
  

I thought if you compile a Visual-studio 2013 Win32 project using `/MT` Code Generation->Runtime library then it will automatically package all dependency dll's - including 3rd party dll's - into the executable?

LIBEAY32.dll is missing

I am linking the static OpenSSL libraries so shouldn't I not need to distribute the dll with my installer? Shouldnt it be packaged into the exe?

My Linker->Input->Additional Dependencies are:

C:\OpenSSL-Win32\lib\VC\static\libeay32MTd.lib

C:\OpenSSL-Win32\lib\VC\static\libeay32MT.lib

C:\OpenSSL-Win32\lib\VC\static\libeay32MD.lib

C:\OpenSSL-Win32\lib\VC\static\libeay32MDd.lib

C:\OpenSSL-Win32\lib\VC\static\ssleay32MTd.lib

C:\OpenSSL-Win32\lib\VC\static\ssleay32MT.lib

C:\OpenSSL-Win32\lib\VC\static\ssleay32MD.lib

C:\OpenSSL-Win32\lib\VC\static\ssleay32MDd.lib

Typically, that error code usually deals with conflicts for 32 and 64-bit libraries. Had this issue occur several times, sometimes because the dll being loaded is for the wrong arch, other times because a 32-bit exe header is missing information necessary to be run on a 64-bit version of Windows.

Excuse me if I am ignorant of this, but I noticed that there is a 32 at the end of each library. Are you compiling for 64-bit or just compiling on a 64-bit Windows installation? If it's the latter, have you run into the same issue on 32-bit Windows?

I am linking the static OpenSSL libraries so shouldn't I not need to distribute the dll with my installer? Shouldnt it be packaged into the exe?

My Linker->Input->Additional Dependencies are:

C:\OpenSSL-Win32\lib\VC\static\libeay32MTd.lib

...

C:\OpenSSL-Win32\lib\VC\static\libeay32MD.lib

C:\OpenSSL-Win32\lib\VC\static\libeay32MDd.lib

C:\OpenSSL-Win32\lib\VC\static\ssleay32MTd.lib

...

C:\OpenSSL-Win32\lib\VC\static\ssleay32MD.lib

C:\OpenSSL-Win32\lib\VC\static\ssleay32MDd.lib

Bear in mind that libraries with a "d" at the end are generally debug libraries, and you probably don't want them being used in the release version of your code.

Quoted for truth. Too easy to assume one is already aware of this.

Shogun.

Are you compiling for 64-bit or just compiling on a 64-bit Windows installation?

I am compiling just using the 32bit static libraries (on my 64bit Windows 8.1 OS) in the hopes that I can just cover everyone (correct me if I am wrong about this?). My application is a simple WinAPI c++ utility application. So it's small (<800kb) so it doesn't make sense to distribute the visual c++ redistributable package with my installer. What I am hoping is to package all dependencies (I only use static libraries) into my .exe if possible.