[LLVMdev] [PATCH] MSVC: Allow choosing different CRT for different build types

nobled nobled at dreamwidth.org
Tue Aug 3 05:43:48 PDT 2010

Óscar Fuentes <ofv at wanadoo.es> wrote:
> I'm a bit wary about this patch. So much complexity for so petty
> feature... Maybe the right thing is to determine the scenarios where
> people set LLVM_USE_CRT. Maybe all we need is to define another build
> type that inherits from Release which uses the debug version of the CRT.
> Anyways, the patch have some issues: remove commented-out code, use the
> `foreach' instead of `FOREACH', as in the rest of the code (same for
> other keywords), either remove the user-configurable variable
> LLVM_USE_CRT or exit with an error if the user sets it, add an extensive
> comment about the motivation of the code and about how it achieves its
> purpose. Maybe put it on a new file under cmake/modules for stuff
> specific of Visual Studio.
Sure; fixed-up version attached.

> But first I'll like to see if we can simplify the requirements.
> [snip]
I'm not sure it's possible to simplify it too much--we still need the
choice between dynamic and static CRT, too. Like Mesa/Gallium3d: by
default CMake has LLVM compiled with the dynamically linked CRT, but
Gallium needs a static CRT and right now it expects LLVM's Debug build
to use /MTd and Release to use /MT. If we add a bunch of new
build-types like DebugStatic, ReleaseStatic, ReleaseStaticDebug, etc
for all the use cases, it seems like it'd end up just as complicated
as having a separate option for each type.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: add-build-config-crt-selection-v8.patch
Type: text/x-patch
Size: 4889 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100803/bb0f49e6/attachment.bin>

More information about the llvm-dev mailing list