CryptoPro
/
core-setup
зеркало из https://github.com/CryptoPro/core-setup.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
core-setup/RepoDirectories.props

36 строки
2.2 KiB
Plaintext
Исходник Обычный вид История

Move common repo directories to isolated props file. Also remove the dev machine BuildNumberMinor workaround per PR feedback, as this is no longer necessary.
2017-06-09 01:00:31 +03:00
<Project ToolsVersion="12.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
<RepoRoot>$(MSBuildThisFileDirectory)</RepoRoot>
<!-- ProjectDir needs to be set for build-tools and legacy usages. New usages should use RepoRoot -->
<ProjectDir>$(RepoRoot)</ProjectDir>
<SourceDir>$(RepoRoot)src/</SourceDir>
<!-- Output directories -->
<BinDir Condition="'$(BinDir)'==''">$(RepoRoot)Bin/</BinDir>
<BaseOutputPath Condition="'$(BaseOutputPath)'==''">$(BinDir)</BaseOutputPath>
<ObjDir Condition="'$(ObjDir)'==''">$(BinDir)obj/</ObjDir>
<BaseIntermediateOutputPath Condition="'$(BaseIntermediateOutputPath)'==''">$(ObjDir)</BaseIntermediateOutputPath>
<!-- Input Directories -->
Respect DotNetRestorePackagesPath if it is set
2017-09-29 22:41:19 +03:00
<PackagesDir>$(DotNetRestorePackagesPath)</PackagesDir>
Move common repo directories to isolated props file. Also remove the dev machine BuildNumberMinor workaround per PR feedback, as this is no longer necessary.
2017-06-09 01:00:31 +03:00
<PackagesDir Condition="'$(PackagesDir)'==''">$(RepoRoot)packages/</PackagesDir>
<ToolRuntimePath Condition="'$(ToolRuntimePath)'==''">$(RepoRoot)Tools/</ToolRuntimePath>
<LocalToolRuntimePath Condition="'$(LocalToolRuntimePath)' == ''">$(ToolRuntimePath)local/</LocalToolRuntimePath>
<ToolsDir Condition="'$(UseToolRuntimeForToolsDir)'=='true'">$(ToolRuntimePath)</ToolsDir>
<ToolsDir Condition="'$(ToolsDir)'==''">$(RepoRoot)Tools/</ToolsDir>
<BuildToolsTaskCoreDir>$(ToolsDir)</BuildToolsTaskCoreDir>
<BuildToolsTaskDesktopDir>$(ToolsDir)net46/</BuildToolsTaskDesktopDir>
<BuildToolsTaskDir>$(BuildToolsTaskCoreDir)</BuildToolsTaskDir>
<BuildToolsTaskDir Condition="'$(MSBuildRuntimeType)' != 'Core'">$(BuildToolsTaskDesktopDir)</BuildToolsTaskDir>
Handle msbuild package breaking changes We need to move our task library to consume netstandard2.0 and net46 as min targets now as msbuild has reset their min frameworks to those. - Convert core-setup.task project to be SDK based - Update output directories for the build - Clean-up project based on new targets
2018-04-02 22:15:20 +03:00
<LocalBuildToolsTaskDir>$(LocalToolRuntimePath)netstandard2.0/</LocalBuildToolsTaskDir>
Move common repo directories to isolated props file. Also remove the dev machine BuildNumberMinor workaround per PR feedback, as this is no longer necessary.
2017-06-09 01:00:31 +03:00
<LocalBuildToolsTaskDir Condition="'$(MSBuildRuntimeType)' != 'Core'">$(LocalToolRuntimePath)net46/</LocalBuildToolsTaskDir>
<PackagingTaskDir Condition="'$(BuildToolsTaskDir)' != ''">$(BuildToolsTaskDir)</PackagingTaskDir>
<DotnetCliPath Condition="'$(DotnetCliPath)'==''">$(ToolsDir)dotnetcli/</DotnetCliPath>
</PropertyGroup>
Handle RIDs better during the build. Currently, when building non-portable on a win10 machine, core-setup restores and produces `win7` RID assets. This causes problems in source-build since corefx produces `win10` assets on the same machine. Thus, core-setup can't use the corefx assets because win10 is not compatible with win7. In fixing this, I refactored the way RIDs are handled during the build. We have 3 main RID usages: * What is the RID of the current machine? $(HostMachineRid) * What is the RID of the toolset we are using to build? core-setup doesn't have this scenario yet, but corefx calls this $(ToolRuntimeRID) * What is the RID that the current build is producing outputs for? $(OutputRid)
2017-10-03 23:54:10 +03:00
<PropertyGroup>
<HostMachineInfoProps>$(BaseIntermediateOutputPath)HostMachineInfo.props</HostMachineInfoProps>
</PropertyGroup>
Move common repo directories to isolated props file. Also remove the dev machine BuildNumberMinor workaround per PR feedback, as this is no longer necessary.
2017-06-09 01:00:31 +03:00
</Project>