diff options
| author | Matt Ellis <matell@microsoft.com> | 2015-11-10 15:05:29 -0800 |
|---|---|---|
| committer | Matt Ellis <matell@microsoft.com> | 2015-11-10 15:05:29 -0800 |
| commit | cdf08854181bae6dc43eb49bea7c88208499679d (patch) | |
| tree | 6431e7fc00fbae59c2b46e17c96033173e1052fc /Documentation | |
| parent | e487749d77066732aacd4a57deb60edbe97883f7 (diff) | |
| download | coreclr-cdf08854181bae6dc43eb49bea7c88208499679d.tar.gz coreclr-cdf08854181bae6dc43eb49bea7c88208499679d.tar.bz2 coreclr-cdf08854181bae6dc43eb49bea7c88208499679d.zip | |
Update testing instructions
The how to test with a custom runtime instructions had gotten stale
since CoreFX no longer consumes the runtime package we produce (it
instead uses the official packages).
Since we can not yet build these packages here, we need to update the
instructions to use BUILDTOOLS_OVERRIDE_RUNTIME in order to be able to
deploy a custom runtime at test time.
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/building/testing-with-corefx.md | 20 |
1 files changed, 2 insertions, 18 deletions
diff --git a/Documentation/building/testing-with-corefx.md b/Documentation/building/testing-with-corefx.md index c16de63dba..ab1bc3045d 100644 --- a/Documentation/building/testing-with-corefx.md +++ b/Documentation/building/testing-with-corefx.md @@ -5,25 +5,9 @@ It may be valuable to use CoreFX tests to validate your changes to CoreCLR or ms **Windows** -In order to do this you need to create a file called `localpublish.props` under the `<repo root>\packages` folder. -The contents of the file should look like this (make sure to update the version to the current version of the CoreCLR package used by CoreFx): +As part of building tests, CoreFX restores a copy of the runtime from myget, in order to update the runtime that is deployed, a special build property `BUILDTOOLS_OVERRIDE_RUNTIME` can be used. If this is set, the CoreFX testing targets will copy all the files in the folder it points to into the test folder, overwriting any files that exist. -```xml -<Project ToolsVersion="12.0" DefaultTargets="Build" - xmlns="http://schemas.microsoft.com/developer/msbuilding/2003"> - <ItemGroup> - <LocalPackages Include="$(PackagesBinDir)"> - <PackageName>Microsoft.DotNet.CoreCLR</PackageName> - <PackageVersion>1.0.2-prerelease</PackageVersion> - <InstallLocation><corefx repo root>\packages</InstallLocation> - </LocalPackages> - </ItemGroup> -</Project> -``` - -Once this file is there, subsequent builds of the CoreCLR repo will install the CoreCLR package into the location specified by `InstallLocation`. - -To run tests, follow the procedure for [running tests in CoreFX](https://github.com/dotnet/corefx/blob/master/Documentation/building/windows-instructions.md). +To run tests, follow the procedure for [running tests in CoreFX](https://github.com/dotnet/corefx/blob/master/Documentation/building/windows-instructions.md). You can pass `/p:BUILDTOOLS_OVERRIDE_RUNTIME=<path-to-coreclr>\bin\Product\Windows_NT.x64.Release` to build.cmd to set this property. **Linux, OS X, FreeBSD** |