libzmq/builds/msvc/properties/Common.props

<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  
  <PropertyGroup>
    <_PropertySheetDisplayName>Common Settings</_PropertySheetDisplayName>
    <CharacterSet>Unicode</CharacterSet>
  </PropertyGroup>

  <ImportGroup Label="PropertySheets">
    <Import Project="$(Platform).props" />
  </ImportGroup>  

  <ItemDefinitionGroup>
    <ClCompile>
      <MultiProcessorCompilation>true</MultiProcessorCompilation>
      <PreprocessorDefinitions>UNICODE;_UNICODE;%(PreprocessorDefinitions)</PreprocessorDefinitions>
      <WarningLevel>Level3</WarningLevel>
    </ClCompile>
  </ItemDefinitionGroup>

  <!-- When using a tool set to target Windows XP, define a pre-processor definition and modify the target Windows version -->
  <ItemDefinitionGroup Condition="$(PlatformToolset.Contains('_xp'))">
    <ClCompile>
      <PreprocessorDefinitions>ZMQ_HAVE_WINDOWS_TARGET_XP;_WIN32_WINNT=0x0501;%(PreprocessorDefinitions)</PreprocessorDefinitions>
    </ClCompile>
  </ItemDefinitionGroup>

</Project>
Added MSVC10 solution and project files for Windows These include configurations for both Win32 and x64 platforms. All project settings have been normalised in property sheets (the ".props" files under builds/msvc/properties) to simplify maintenance. Build artefacts are all generated in platform-specific subfolders of bin, lib and obj directories. Also enables the use of precompiled headers with MSVC10. This significantly reduces the time required to compile libzmq with Visual Studio on Windows. It should have no impact on other platforms. Signed-off-by: Stuart Webster <sw_webster@hotmail.com> 2011-12-15 14:03:43 +01:00			`<?xml version="1.0" encoding="utf-8"?>`
Remove versioning from VS .props files. 2014-04-15 04:18:36 +02:00			`<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">`
Rationalize and update Visual Studio projects and packaging. 2014-04-06 11:39:15 +02:00
Added MSVC10 solution and project files for Windows These include configurations for both Win32 and x64 platforms. All project settings have been normalised in property sheets (the ".props" files under builds/msvc/properties) to simplify maintenance. Build artefacts are all generated in platform-specific subfolders of bin, lib and obj directories. Also enables the use of precompiled headers with MSVC10. This significantly reduces the time required to compile libzmq with Visual Studio on Windows. It should have no impact on other platforms. Signed-off-by: Stuart Webster <sw_webster@hotmail.com> 2011-12-15 14:03:43 +01:00			`<PropertyGroup>`
			`<_PropertySheetDisplayName>Common Settings</_PropertySheetDisplayName>`
Rationalize and update Visual Studio projects and packaging. 2014-04-06 11:39:15 +02:00			`<CharacterSet>Unicode</CharacterSet>`
Added MSVC10 solution and project files for Windows These include configurations for both Win32 and x64 platforms. All project settings have been normalised in property sheets (the ".props" files under builds/msvc/properties) to simplify maintenance. Build artefacts are all generated in platform-specific subfolders of bin, lib and obj directories. Also enables the use of precompiled headers with MSVC10. This significantly reduces the time required to compile libzmq with Visual Studio on Windows. It should have no impact on other platforms. Signed-off-by: Stuart Webster <sw_webster@hotmail.com> 2011-12-15 14:03:43 +01:00			`</PropertyGroup>`
Rationalize and update Visual Studio projects and packaging. 2014-04-06 11:39:15 +02:00
Optimize VS projects and common props. 2014-05-13 12:17:48 +02:00			`<ImportGroup Label="PropertySheets">`
			`<Import Project="$(Platform).props" />`
			`</ImportGroup>`

Added MSVC10 solution and project files for Windows These include configurations for both Win32 and x64 platforms. All project settings have been normalised in property sheets (the ".props" files under builds/msvc/properties) to simplify maintenance. Build artefacts are all generated in platform-specific subfolders of bin, lib and obj directories. Also enables the use of precompiled headers with MSVC10. This significantly reduces the time required to compile libzmq with Visual Studio on Windows. It should have no impact on other platforms. Signed-off-by: Stuart Webster <sw_webster@hotmail.com> 2011-12-15 14:03:43 +01:00			`<ItemDefinitionGroup>`
			`<ClCompile>`
			`<MultiProcessorCompilation>true</MultiProcessorCompilation>`
Rationalize and update Visual Studio projects and packaging. 2014-04-06 11:39:15 +02:00			`<PreprocessorDefinitions>UNICODE;_UNICODE;%(PreprocessorDefinitions)</PreprocessorDefinitions>`
			`<WarningLevel>Level3</WarningLevel>`
Added MSVC10 solution and project files for Windows These include configurations for both Win32 and x64 platforms. All project settings have been normalised in property sheets (the ".props" files under builds/msvc/properties) to simplify maintenance. Build artefacts are all generated in platform-specific subfolders of bin, lib and obj directories. Also enables the use of precompiled headers with MSVC10. This significantly reduces the time required to compile libzmq with Visual Studio on Windows. It should have no impact on other platforms. Signed-off-by: Stuart Webster <sw_webster@hotmail.com> 2011-12-15 14:03:43 +01:00			`</ClCompile>`
			`</ItemDefinitionGroup>`
Rationalize and update Visual Studio projects and packaging. 2014-04-06 11:39:15 +02:00
Fixes for Windows XP compatibility A Visual Studio build from master (commit id: dac5b45dfb224ff184a7aed39c5859ae5bac3803) using the v140_xp toolset yields a binary that is not XP compatible. Two libraries contain exports that cannot be found: - IPHLPAPI.DLL : if_nametoindex - KERNEL32.DLL : InitializeConditionVariable The latter export is already dealt with in the file './src/condition_variable.hpp'; however this requires setting the _WIN32_WINNT pre-processor definition. I am not experienced enough to figure a work around for the 'if_nametoindex' method, so I have created a new pre-processor definition 'ZMQ_HAVE_WINDOWS_TARGET_XP' and removed the calling of the function with the limitation that these builds cannot handle a IPv6 address with an adapter name. To make it easier for people targeting XP with an MSVC build I have modified the MSBuild property file to add/modify the pre-processor definitions if they are building using a XP targeting tool set; such as v140_xp. 2016-03-31 16:45:00 +02:00			`<!-- When using a tool set to target Windows XP, define a pre-processor definition and modify the target Windows version -->`
			`<ItemDefinitionGroup Condition="$(PlatformToolset.Contains('_xp'))">`
			`<ClCompile>`
			`<PreprocessorDefinitions>ZMQ_HAVE_WINDOWS_TARGET_XP;_WIN32_WINNT=0x0501;%(PreprocessorDefinitions)</PreprocessorDefinitions>`
			`</ClCompile>`
			`</ItemDefinitionGroup>`

Added MSVC10 solution and project files for Windows These include configurations for both Win32 and x64 platforms. All project settings have been normalised in property sheets (the ".props" files under builds/msvc/properties) to simplify maintenance. Build artefacts are all generated in platform-specific subfolders of bin, lib and obj directories. Also enables the use of precompiled headers with MSVC10. This significantly reduces the time required to compile libzmq with Visual Studio on Windows. It should have no impact on other platforms. Signed-off-by: Stuart Webster <sw_webster@hotmail.com> 2011-12-15 14:03:43 +01:00			`</Project>`