# CMP0136

Added in version 3.24.

Watcom runtime library flags are selected by an abstraction.

Compilers targeting the Watcom ABI have flags to select the Watcom runtime library.

In CMake 3.23 and below, Watcom runtime library selection flags are added to the default `CMAKE_<LANG>_FLAGS_<CONFIG>` cache entries by CMake automatically. This allows users to edit their cache entries to adjust the flags. However, the presence of such default flags is problematic for projects that want to choose a different runtime library programmatically. In particular, it requires string editing of the `CMAKE_<LANG>_FLAGS_<CONFIG>` variables with knowledge of the CMake builtin defaults so they can be replaced.

CMake 3.24 and above prefer to leave the Watcom runtime library selection flags out of the default `CMAKE_<LANG>_FLAGS_<CONFIG>` values and instead offer a first-class abstraction. The `CMAKE_WATCOM_RUNTIME_LIBRARY` variable and `WATCOM_RUNTIME_LIBRARY` target property may be set to select the Watcom runtime library. If they are not set then CMake uses the default value `MultiThreadedDLL` on Windows and `SingleThreaded` on other platforms, which is equivalent to the original flags.

This policy provides compatibility with projects that have not been updated to be aware of the abstraction. The policy setting takes effect as of the first `project()` or `enable_language()` command that enables a language whose compiler targets the Watcom ABI.

Note

Once the policy has taken effect at the top of a project, that choice must be used throughout the tree. In projects that have nested projects in subdirectories, be sure to convert everything together.

The `OLD` behavior for this policy is to place Watcom runtime library flags in the default `CMAKE_<LANG>_FLAGS_<CONFIG>` cache entries and ignore the `CMAKE_WATCOM_RUNTIME_LIBRARY` abstraction. The `NEW` behavior for this policy is to not place Watcom runtime library flags in the default cache entries and use the abstraction instead.

This policy was introduced in CMake version 3.24. It may be set by `cmake_policy()` or `cmake_minimum_required()`. If it is not set, CMake does not warn, and uses `OLD` behavior.

Note

The `OLD` behavior of a policy is `deprecated by definition` and may be removed in a future version of CMake.