Thread: Visual C++ 2008 static linking help

I know this is about VC++ specifically, but I just don't trust Microsoft's boards that much. Plus I know the past several articles on the main page dealt with VC++.

Anyway, VC++-compiled binaries seem to enforce that I use the MSVC 9.0 runtime DLLs and manifest file regardless if I specify multi-threaded (or debug) or multi-threaded DLL (or debug). I know this because the statically-linked runtime in my binary seemed to work on my computer, but when I transferred it to my parents' computer, the binary began whining about the absence of the runtime DLLs. It worked on my computer because VC++ installs the runtime DLLs of course.

I just don't want to force people who use my software to install runtimes. Sure, for many, it's not that big a deal. But the general population would see this requirement and not bother. Also, if I were to distribute the runtime, that would make for a bigger download. Likely I want to make more than one project, and I don't want to distribute the runtime in every single download.

Any help is appreciated!

Well, you mentioned solution #1 in your title, link statically.

That's makes your executable larger, but you have no dependencies at that point. The size increase to your executable is related to the functions the compiler pulls in from the library, but it is probably smaller than the redistributable package.

Another solution is not to use MFC.

Of course, that means either another framework, which isn't a bad idea, but also has the same issue of increasing the target size vs a DLL which you would package as part of your install, depending on the framework you choose.

Did you have a question on how to statically link MFC?

Well, I use Express, which is MFC-less. I mean the C runtime itself being statically linkED.

I'll give it another shot and post any errors I get on my other computer.