cheng/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
68a8d6a11c
wxWidgets/build/msw/wx_setup.props

118 lines
5.6 KiB
Plaintext
Raw Normal View History

Mark MSVS *.props files as using CR LF as well. For consistency with *.vcxproj and *.sln.
2015-03-19 16:43:29 -04:00
<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
Use nicer labels for wxWidgets property sheets in MSVS UI No real changes, just use the same _PropertySheetDisplayName element as the standard style sheets use to show a slightly more user-friendly label in the Property Sheet manager window in MSVS.
2021-04-14 10:44:09 -04:00
<PropertyGroup>
<_PropertySheetDisplayName>wxWidgets Setup Options</_PropertySheetDisplayName>
</PropertyGroup>
Mark MSVS *.props files as using CR LF as well. For consistency with *.vcxproj and *.sln.
2015-03-19 16:43:29 -04:00
<PropertyGroup Label="UserMacros">
Upgrade version to 3.1.6 Run misc/scripts/inc_release, bakefile_gen and autoconf.
2021-04-14 11:57:27 -04:00
<wxVersionString>316</wxVersionString>
Mark MSVS *.props files as using CR LF as well. For consistency with *.vcxproj and *.sln.
2015-03-19 16:43:29 -04:00
<wxShortVersionString>31</wxShortVersionString>
<wxToolkitPrefix>msw</wxToolkitPrefix>
<wxCompilerPrefix>vc</wxCompilerPrefix>
<wxCfg>
</wxCfg>
<wxVendor>custom</wxVendor>
</PropertyGroup>
<PropertyGroup Label="UserMacros" Condition="'$(Platform)'=='Win32'">
<wxArchSuffix>
</wxArchSuffix>
</PropertyGroup>
<PropertyGroup Label="UserMacros" Condition="'$(Platform)'=='x64'">
<wxArchSuffix>_x64</wxArchSuffix>
</PropertyGroup>
Introduce MSW ARM64 support This is a preliminary ARM64 platform support for wxWidgets at "it compiles" stage. This will allow building and testing wxWidgets based apps for oncoming Windows 10 ARM64. Requirements: - Visual Studio 2017 Update 4 or later with Visual C++ compilers and libraries for ARM64 component installed Building: 1. Open command prompt. 2. Change directory to build\msw subfolder. 3. Run "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvarsamd64_arm64.bat" once. 4. Use `nmake TARGET_CPU=ARM64 ...` to build required flavor of wxWidget libraries. Notes: 1. Building of *.sln/*.vcxproj files does not support ARM64 yet. This requires to hardcode Windows SDK to 10.0.15063.0 or later in *.vcxproj files, which would render them non-compilable in older Visual Studio versions. Microsoft is aware of this issue and is planning a fix in the next version of Visual Studio. 2. wxmsw31ud_gl.dll does not build yet. Awaiting Microsoft to deliver missing opengl32.lib for ARM64. Please, specify USE_OPENGL=0. Closes https://github.com/wxWidgets/wxWidgets/pull/923
2018-09-17 16:34:32 -04:00
<PropertyGroup Label="UserMacros" Condition="'$(Platform)'=='ARM64'">
<wxArchSuffix>_arm64</wxArchSuffix>
</PropertyGroup>
Mark MSVS *.props files as using CR LF as well. For consistency with *.vcxproj and *.sln.
2015-03-19 16:43:29 -04:00
<PropertyGroup Label="UserMacros" Condition="'$(Platform)'=='Itanium'">
<wxArchSuffix>_ia64</wxArchSuffix>
</PropertyGroup>
<PropertyGroup Label="UserMacros" Condition="('$(Configuration)'=='Debug' or '$(Configuration)'=='DLL Debug') and '$(CharacterSet)'=='Unicode'">
<wxSuffix>ud</wxSuffix>
</PropertyGroup>
<PropertyGroup Label="UserMacros" Condition="('$(Configuration)'=='Debug' or '$(Configuration)'=='DLL Debug') and '$(CharacterSet)'!='Unicode'">
<wxSuffix>d</wxSuffix>
</PropertyGroup>
<PropertyGroup Label="UserMacros" Condition="('$(Configuration)'=='Release' or '$(Configuration)'=='DLL Release') and '$(CharacterSet)'=='Unicode'">
<wxSuffix>u</wxSuffix>
</PropertyGroup>
<PropertyGroup Label="UserMacros" Condition="('$(Configuration)'=='Release' or '$(Configuration)'=='DLL Release') and '$(CharacterSet)'!='Unicode'">
<wxSuffix>
</wxSuffix>
</PropertyGroup>
<PropertyGroup Label="UserMacros" Condition="'$(Configuration)'=='Debug' or '$(Configuration)'=='DLL Debug'">
<wxSuffixDebug>d</wxSuffixDebug>
</PropertyGroup>
<PropertyGroup Label="UserMacros" Condition="'$(Configuration)'!='Debug' and '$(Configuration)'!='DLL Debug'">
<wxSuffixDebug>
</wxSuffixDebug>
</PropertyGroup>
Define wxOutDirName variables in MSVS properties file This will be useful for allowing other projects, not necessarily located at the same level of the file hierarchy as the projects for building the library, to refer to the location of the libraries more easily.
2016-02-05 15:31:31 -05:00
<PropertyGroup Label="UserMacros" Condition="'$(Configuration)'=='DLL Debug' or '$(Configuration)'=='DLL Release'">
<wxLibTypeSuffix>dll</wxLibTypeSuffix>
Mark MSVS *.props files as using CR LF as well. For consistency with *.vcxproj and *.sln.
2015-03-19 16:43:29 -04:00
</PropertyGroup>
Define wxOutDirName variables in MSVS properties file This will be useful for allowing other projects, not necessarily located at the same level of the file hierarchy as the projects for building the library, to refer to the location of the libraries more easily.
2016-02-05 15:31:31 -05:00
<PropertyGroup Label="UserMacros" Condition="'$(Configuration)'!='DLL Debug' and '$(Configuration)'!='DLL Release'">
<wxLibTypeSuffix>lib</wxLibTypeSuffix>
Mark MSVS *.props files as using CR LF as well. For consistency with *.vcxproj and *.sln.
2015-03-19 16:43:29 -04:00
</PropertyGroup>
Define wxOutDirName variables in MSVS properties file This will be useful for allowing other projects, not necessarily located at the same level of the file hierarchy as the projects for building the library, to refer to the location of the libraries more easily.
2016-02-05 15:31:31 -05:00
<PropertyGroup Label="UserMacros">
<wxOutDirName>$(wxCompilerPrefix)$(wxArchSuffix)_$(wxLibTypeSuffix)$(wxCfg)</wxOutDirName>
<wxOutDir>..\..\lib\$(wxOutDirName)\</wxOutDir>
Mark MSVS *.props files as using CR LF as well. For consistency with *.vcxproj and *.sln.
2015-03-19 16:43:29 -04:00
</PropertyGroup>
<PropertyGroup Label="UserMacros" Condition="'$(Configuration)'=='DLL Debug'">
<wxIntRootDir>$(wxCompilerPrefix)$(wxArchSuffix)_$(wxToolkitPrefix)$(wxSuffix)dll\</wxIntRootDir>
</PropertyGroup>
<PropertyGroup Label="UserMacros" Condition="'$(Configuration)'=='DLL Release'">
<wxIntRootDir>$(wxCompilerPrefix)$(wxArchSuffix)_$(wxToolkitPrefix)$(wxSuffix)dll\</wxIntRootDir>
</PropertyGroup>
<PropertyGroup Label="UserMacros" Condition="'$(Configuration)'=='Debug'">
<wxIntRootDir>$(wxCompilerPrefix)$(wxArchSuffix)_$(wxToolkitPrefix)$(wxSuffix)\</wxIntRootDir>
</PropertyGroup>
<PropertyGroup Label="UserMacros" Condition="'$(Configuration)'=='Release'">
<wxIntRootDir>$(wxCompilerPrefix)$(wxArchSuffix)_$(wxToolkitPrefix)$(wxSuffix)\</wxIntRootDir>
</PropertyGroup>
<PropertyGroup Label="UserMacros">
<wxIncSubDir>$(wxToolkitPrefix)$(wxSuffix)</wxIncSubDir>
Use long version string in the DLL names in MSVS 201x projects This makes them compatible with the makefiles and MSVS 200x projects. Notice that wxVersionString will need to be set to "32", not "320", when 3.2.0 release is done, as the micro version component is only used in the DLL names for the development releases but not stable ones.
2016-03-03 13:31:44 -05:00
<wxToolkitDllNamePrefix>wx$(wxToolkitPrefix)$(wxVersionString)$(wxSuffix)_</wxToolkitDllNamePrefix>
Mark MSVS *.props files as using CR LF as well. For consistency with *.vcxproj and *.sln.
2015-03-19 16:43:29 -04:00
<wxToolkitDllNameSuffix>_$(wxCompilerPrefix)$(wxArchSuffix)_$(wxVendor)</wxToolkitDllNameSuffix>
<wxToolkitLibNamePrefix>wx$(wxToolkitPrefix)$(wxShortVersionString)$(wxSuffix)_</wxToolkitLibNamePrefix>
Use long version string in the DLL names in MSVS 201x projects This makes them compatible with the makefiles and MSVS 200x projects. Notice that wxVersionString will need to be set to "32", not "320", when 3.2.0 release is done, as the micro version component is only used in the DLL names for the development releases but not stable ones.
2016-03-03 13:31:44 -05:00
<wxBaseDllNamePrefix>wxbase$(wxVersionString)$(wxSuffix)</wxBaseDllNamePrefix>
Mark MSVS *.props files as using CR LF as well. For consistency with *.vcxproj and *.sln.
2015-03-19 16:43:29 -04:00
<wxBaseLibNamePrefix>wxbase$(wxShortVersionString)$(wxSuffix)</wxBaseLibNamePrefix>
</PropertyGroup>
<ItemDefinitionGroup>
Don't use thread-safe statics with MSVS when targeting XP Disable thread-safe initialization for static local variables in Visual Studio 2015 when XP toolset is used as this results in crashes when using DLLs under XP, see #13116. Closes #17403.
2016-07-01 11:24:27 -04:00
<ClCompile>
<AdditionalOptions Condition="'$(PlatformToolset)' == 'v140_xp'">/Zc:threadSafeInit- %(AdditionalOptions)</AdditionalOptions>
Enable standard-confirming new behaviour in MSVS 201x projects Use /Zc:throwingNew option for the compilers supporting it instead of defaulting to compatible behaviour, which assumes that operator new can return NULL on allocation failure, that we don't need, at least in the release builds. This is also slightly more efficient as it allows the compiler to avoid generating null checks after calling new. Closes #19069.
2021-01-31 17:16:46 -05:00
<AdditionalOptions Condition="('$(Configuration)'=='Release' or '$(Configuration)'=='DLL Release') and '$(VisualStudioVersion)' >= '14.0'">/Zc:throwingNew %(AdditionalOptions)</AdditionalOptions>
Don't use thread-safe statics with MSVS when targeting XP Disable thread-safe initialization for static local variables in Visual Studio 2015 when XP toolset is used as this results in crashes when using DLLs under XP, see #13116. Closes #17403.
2016-07-01 11:24:27 -04:00
</ClCompile>
Mark MSVS *.props files as using CR LF as well. For consistency with *.vcxproj and *.sln.
2015-03-19 16:43:29 -04:00
<Link>
Link with shlwapi.lib and version.lib under MSW These libraries are required now that we don't load the functions from them dynamically (see e78be14ac185508bfff4a8e515c2efe80629603d) Closes #17180
2015-10-07 12:31:43 -04:00
<AdditionalDependencies>kernel32.lib;user32.lib;gdi32.lib;comdlg32.lib;winspool.lib;shell32.lib;shlwapi.lib;ole32.lib;oleaut32.lib;uuid.lib;advapi32.lib;version.lib;comctl32.lib;rpcrt4.lib;wsock32.lib;wininet.lib;winmm.lib;%(AdditionalDependencies)</AdditionalDependencies>
Mark MSVS *.props files as using CR LF as well. For consistency with *.vcxproj and *.sln.
2015-03-19 16:43:29 -04:00
</Link>
</ItemDefinitionGroup>
<ItemGroup>
<BuildMacro Include="wxShortVersionString">
<Value>$(wxShortVersionString)</Value>
</BuildMacro>
<BuildMacro Include="wxArchSuffix">
<Value>$(wxArchSuffix)</Value>
</BuildMacro>
<BuildMacro Include="wxToolkitPrefix">
<Value>$(wxToolkitPrefix)</Value>
</BuildMacro>
<BuildMacro Include="wxCompilerPrefix">
<Value>$(wxCompilerPrefix)</Value>
</BuildMacro>
<BuildMacro Include="wxCfg">
<Value>$(wxCfg)</Value>
</BuildMacro>
<BuildMacro Include="wxVendor">
<Value>$(wxVendor)</Value>
</BuildMacro>
<BuildMacro Include="wxOutDir">
<Value>$(wxOutDir)</Value>
</BuildMacro>
Define wxOutDirName variables in MSVS properties file This will be useful for allowing other projects, not necessarily located at the same level of the file hierarchy as the projects for building the library, to refer to the location of the libraries more easily.
2016-02-05 15:31:31 -05:00
<BuildMacro Include="wxOutDirName">
<Value>$(wxOutDirName)</Value>
</BuildMacro>
Mark MSVS *.props files as using CR LF as well. For consistency with *.vcxproj and *.sln.
2015-03-19 16:43:29 -04:00
<BuildMacro Include="wxIntRootDir">
<Value>$(wxIntRootDir)</Value>
</BuildMacro>
</ItemGroup>
</Project>
Reference in New Issue Copy Permalink