Roger Leigh commented on XERCESC-2035:

You can certainly do this by tweaking the various {{CMAKE_CXX_FLAGS_*}} 
variables to change them from their defaults.  We leave them as the defaults 
since using the non-static runtimes is recommended and most people will want 
that.  But there's nothing to stop an end user from tweaking these when running 
cmake; either by passing in {{-DCMAKE_CXX_FLAGS_XXX=...}} on the command-line 
or by editing the script.  Newer cmake versions let you set the "Platform 
Toolset" on top of this.  It's not something I've played with much; I've 
generally stuck to the defaults unless I had a good reason to change things.

> Add Windows build configs with static MSVC CRT linkage
> ------------------------------------------------------
>                 Key: XERCESC-2035
>                 URL: https://issues.apache.org/jira/browse/XERCESC-2035
>             Project: Xerces-C++
>          Issue Type: Improvement
>          Components: Miscellaneous
>    Affects Versions: 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4
>         Environment: All
>            Reporter: Lee Doron
>            Priority: Minor
>             Fix For: 3.2.0
> The Windows DLL builds (e.g. Debug and Release) currently are linked against 
> the Microsoft Visual C++ C Runtime DLLs (using the /MDd and /MD options, 
> respectively). This means that it cannot function without the corresponding 
> MSVCRnnn.DLL file, so the end user must install the proper Microsoft Visual 
> C++ Redistributable.
> Please consider adding build configurations that are statically linked to the 
> CRT (almost identical to those above, but using the /MTd and /MT options, 
> respectively). This would give developers the option of using a Xerces DLL 
> that doesn't have this dependency on the Redistributable package.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org

Reply via email to