You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Andrew Schwartzmeyer (JIRA)" <ji...@apache.org> on 2017/08/11 22:09:00 UTC
[jira] [Updated] (ZOOKEEPER-2874) Windows Debug builds don't link
with `/MTd`
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Schwartzmeyer updated ZOOKEEPER-2874:
--------------------------------------------
Summary: Windows Debug builds don't link with `/MTd` (was: Windows Debug builds don't link to /MTd)
> Windows Debug builds don't link with `/MTd`
> -------------------------------------------
>
> Key: ZOOKEEPER-2874
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2874
> Project: ZooKeeper
> Issue Type: Bug
> Environment: Windows 10 using CMake
> Reporter: Andrew Schwartzmeyer
> Assignee: Andrew Schwartzmeyer
>
> While not apparent when building ZooKeeper stand-alone, further testing when linking with Mesos revealed it was ZooKeeper that was causing the warning:
> {noformat}
> LIBCMTD.lib(initializers.obj) : warning LNK4098: defaultlib 'libcmt.lib' conflicts with use of other libs; use /NODEFAULTLIB:library [C:\Users\andschwa\src\mesos\build\src\slave\mesos-agent.vcxproj]
> {noformat}
> As Mesos is linking with {{/MTd}} in Debug configuration (which is the most common practice).
> Once I found the source of the warning, the fix is trivial and I am posting a patch.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)