Building a statically linked MFC-App with VC7
-
Using VC6 it was easily possible to create a MFC-VC6 appl. and link MFC statically. The apps only depended on Kernel32.dll, User32.dll,... :) Doing the same with VC7 or even converting such a project from VC6 to VC7 results in additional dependencies to SHLWAPI.dll, OELAUT.dll and OLEACC.dll. :(( How can I remove the dependencies to these DLLs, even linking with /opt:ref /opt:noicf doesn't help.:confused: Any idea on howto make VC7 work like VC6 in this aspect is very much appreciated. Rainer
-
Using VC6 it was easily possible to create a MFC-VC6 appl. and link MFC statically. The apps only depended on Kernel32.dll, User32.dll,... :) Doing the same with VC7 or even converting such a project from VC6 to VC7 results in additional dependencies to SHLWAPI.dll, OELAUT.dll and OLEACC.dll. :(( How can I remove the dependencies to these DLLs, even linking with /opt:ref /opt:noicf doesn't help.:confused: Any idea on howto make VC7 work like VC6 in this aspect is very much appreciated. Rainer
Rainer i too have noticed those dependencies, but don't think shlwapi and oleaut create particular problems as far as oleacc.dll i suggest you to check out: http://www.codeproject.com/cpp/oleaccproxy.asp[^] basically an oleproxy or, better, a delayed loading dll, seems to be a recommended practice maybe you could use this way also with the other 2 dlls hope this helps best regards
-
Rainer i too have noticed those dependencies, but don't think shlwapi and oleaut create particular problems as far as oleacc.dll i suggest you to check out: http://www.codeproject.com/cpp/oleaccproxy.asp[^] basically an oleproxy or, better, a delayed loading dll, seems to be a recommended practice maybe you could use this way also with the other 2 dlls hope this helps best regards
This helps thank you :):) Rainer