diff options
| author | Alex Ghiondea <ghiondea.alexandru@microsoft.com> | 2015-02-18 16:26:30 -0800 |
|---|---|---|
| committer | Alex Ghiondea <ghiondea.alexandru@microsoft.com> | 2015-02-19 11:24:20 -0800 |
| commit | fbc318cfd987694d04431aa4858e299d712af940 (patch) | |
| tree | aee74df1df62da0486580d743a120182c4e9f1c3 /src/build.proj | |
| parent | f846ccff6be6b47f139a6b910cae20de54f54329 (diff) | |
| download | coreclr-fbc318cfd987694d04431aa4858e299d712af940.tar.gz coreclr-fbc318cfd987694d04431aa4858e299d712af940.tar.bz2 coreclr-fbc318cfd987694d04431aa4858e299d712af940.zip | |
Setup the CoreCLR repo to use the LocalPackagePublish mechanism.
This will enable the 'local publish' of the CoreCLR package to a location where
it can be picked up by the CoreFx build. What this means is that you will be able
to build the CoreCLR package and use that to run the CoreFx tests on top of it.
Changes required to make this happen:
- Refactor the managed build to make sure the buildtools gets restored before
we attempt to use the targets it provides.
- Take a dependency to the Microsoft.DotNet.BuildTools to bring in the packages.targets
- Update the $(PackagesDir) to point to the <repo root>\packages to make it consistent with CoreFx
- Hook-up the LocalPackagePublish targets to the build of the CoreCLR NuGet packages
Diffstat (limited to 'src/build.proj')
| -rw-r--r-- | src/build.proj | 41 |
1 files changed, 41 insertions, 0 deletions
diff --git a/src/build.proj b/src/build.proj new file mode 100644 index 0000000000..dff408ea1a --- /dev/null +++ b/src/build.proj @@ -0,0 +1,41 @@ +<Project ToolsVersion="12.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> + <Import Project="..\dir.props"/> + + <!-- List the projects that need to be built --> + <ItemGroup> + <Project Include="mscorlib\mscorlib.csproj" /> + </ItemGroup> + + <Import Project="..\dir.targets" /> + + <Import Project="..\dir.traversal.targets" /> + + + <!-- Hook into the local publishing by providing the task that needs to run before we can do the local publishing --> + <Import Project="$(BuildToolsLocation)\lib\packages.targets" Condition="Exists('$(BuildToolsLocation)\lib\packages.targets')" /> + <PropertyGroup> + <NugetPackageBuildTargets>BuildNuGetPackages</NugetPackageBuildTargets> + </PropertyGroup> + + <!-- Generate Microsoft.Dotnet.CoreCLR nuget package and associated development package --> + <Target Name="BuildNuGetPackages" AfterTargets="MovePDB" Condition="'$(BuildNugetPackage)' != 'false'"> + <MakeDir Directories="$(PackagesBinDir)" Condition="!Exists('$(PackagesBinDir)')" /> + <Copy SourceFiles="@(NuSpecSrcs)" DestinationFolder="$(PackagesBinDir)" /> + <Exec Command=""$(NuGetToolPath)" pack "%(NuSpecs.Identity)" -NoPackageAnalysis -NoDefaultExcludes -OutputDirectory "$(PackagesBinDir)"" /> + </Target> + + <ItemGroup> + <PDBSToMove Include="$(BinDir)mscorlib.pdb"/> + </ItemGroup> + + <PropertyGroup> + <MscorlibPDBPath>$(BinDir)mscorlib.pdb</MscorlibPDBPath> + </PropertyGroup> + + <Target Name="MovePDB" AfterTargets="Build"> + <Move Condition="Exists($(MscorlibPDBPath))" + SourceFiles="@(PDBSToMove)" + DestinationFolder="$(BinDir)PDB" + /> + </Target> +</Project>
\ No newline at end of file |