Programming with ATL and C Run-Time Code
This section discusses the benefits of using the C Run-Time Library (CRT) with either static or dynamic linking, or alternatively using the _ATL_MIN_CRT macro to reduce your dependency on CRT code.
In This Section
- Benefits and Tradeoffs of Using _ATL_MIN_CRT
Summarizes the benefits and tradeoffs involved in linking statically to the CRT, linking dynamically, or avoiding the CRT DLL altogether.
- Linking to the CRT in Your ATL Project
Discusses the project settings and linker options for linking to the CRT; also provides details on how linking to the CRT affects your program image.
- Using _ATL_MIN_CRT in Your ATL Project
Discusses the project settings for using _ATL_MIN_CRT and how this affects your code.
- Recognizing Functions that Rely on CRT Startup Code
Lists functions, compiler options, and libraries that require the CRT startup code.
- Identifying CRT Startup Code Dependencies by Building
Shows how to identify your CRT dependencies by using various build options and examining the output.
- Exception Handling and _ATL_MIN_CRT
Describes how using _ATL_MIN_CRT affects exception handling in ATL projects.
Provides links to conceptual topics on how to program using the Active Template Library.
- Run-Time Library Behavior
Provides details on how the CRT startup code works.
- C Run-Time Libraries
Discusses the various .lib files that comprise the C run-time libraries and lists their associated compiler options and preprocessor directives.