how to avoid linking msvcr100.dll?

Question

I'm using VC++ Express, my application needs msvcr100.dll. The user should have this file in his system, is there any way that my application could avoid the use of these files ?

Yup. Statically link the runtime library as opposed to dynamically linking it. That's available in your project settings. (By the way, do avoid tag-spamming. What does this have to do with assembly, api, or C?) — Bathsheba, Apr 14 '15 at 10:22
How can i do this ? i couldnt find the related settings, thank you for the answer — user2877050, Apr 14 '15 at 10:25
Note that you can just place the DLL in the same directory as your executable. It's not the prettiest solution, but it is quite robust. — MSalters, Apr 14 '15 at 11:50

score 1 · Accepted Answer · edited May 23 '17 at 12:22

1

In project settings, change Runtime Linrary for Release builds to Multi-threaded /MT (as opposed to Multi-threaded DLL /MD). This switches to static runtime library and eliminates the dependency in question.

enter image description here

See also:

edited May 23 '17 at 12:22

Community

1
1

answered Apr 14 '15 at 10:49

Roman R.

64,446
5
83
139

score 0 · Answer 2 · edited May 23 '17 at 11:50

C and C++ standards don´t only define the languages, but some (many) functions and classes, which a system supporting C/C++ should have (at least). A clean Windows installation has only a subset of the necessary things, while this DLL file has everything (but this DLL is not automatically installed).

Three possibilities:
a) Force every user to install the MSVC redistributable package (according to your question, you don´t want that)

b) Distribute the file yourself together with your program. Problematic because version issues etc., and possibly legal problems in some jurisdictions.

c) Enable "static" linking in the project setting. This will put everything in your own EXE file; it will use more memory but isn´t dependent on the external file anymore. Where to find this in VS: How do I make a fully statically linked .exe with Visual Studio Express 2005?

(b) is not not problematic. In fact, it actively prevents version issues. You also have permission from Microsoft, so no legal problems either. — MSalters, Apr 14 '15 at 11:51

how to avoid linking msvcr100.dll?

2 Answers2