Home/ Questions/Q 827395
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T03:34:04+00:00

I’m doing a very small windows application consisting of just a single executable. As

  • 0

I’m doing a very small windows application consisting of just a single executable. As the program will reside on a SD card I want the application to be as self contained as possible, and I’d rather not have an installer. I’d want the user to be able to simply copy the executable to the SD card and be able to run it straight away without fiddling with anything extra. The problem then becomes the fact that my program is compiled with VS 2008 which requires versions of the CRT which I can’t guarantee is installed. I’m linking statically to the CRT, which I incorrectly thought would circumvent this problem. I’ve been thinking of tracking down some older VS version, but I have a feeling this is the incorrect path. I want the program to run on a fresh install of windows xp and above.

Grateful for any help.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Linking statically to the CRT using /MT or /MTd (for debug) should do exactly what you need.

    The fact that it isn’t suggest that there is still something that depends on the dynamic library. That would be the case if you has some additional DLLs which are not compiled with the static CRT.

    you can use the dependency walker (depends.exe) to figure out exactly which dlls use which and who still depends on the dynamic CRT or in any other DLL.

    Another approach is to run your exe from the debugger and see which DLLs are being loaded in the output window. Which depends.exe gives you only the dlls loaded on the startup, this can give you some additional dependencies that are loaded only on runtime.

    • 0