summaryrefslogtreecommitdiff
path: root/dir.props
AgeCommit message (Collapse)AuthorFilesLines
2016-03-04Define Platform and OutputPaths before ↵Gaurav Khanna1-0/+11
Microsoft.Common.CurrentVersion.targets is included.
2016-03-02Upgrade CLI version and buildtools, and make build file changes.Davis Goodin1-2/+4
Unset CORE_ROOT in environment on Windows before doing restore so that dotnet CLI doesn't try to run using binaries from the test CORE_ROOT. Restore the xunit wrapper projects in a batch rather than individually to save a lot of time. Work around xunit.runner.msbuild not having compatible package layout by ignoring errors and adding import so that a future fix will work. Hard-code C# language for generated wrapper projects: the $(Language) property wasn't set. Also Change www.myget.org to dotnet.myget.org, as we switched to enterprise myget. Add System.ObjectModel to tests\src\JIT\config\benchmark+serialize\project.json to manually upgrade it to a version that doesn't require lifting for runtime. This fixes System.ObjectModel.dll being missing from CORE_ROOT and causing the test to fail. Switch to v3 nuget feeds and sync NuGet.Configs.
2016-02-07Change to support Microsoft.NetCore.Runtime.CoreCLR nuget package generation.Gaurav Khanna (CLR)1-7/+27
2016-01-30Fix build break in internal buildJan Kotas1-1/+1
[tfs-changeset: 1570568]
2016-01-29update version of buildtoolsRahul Kumar1-22/+19
2016-01-23Build mscorlib with CoreCLR MSBuild on LinuxJohn Chen1-0/+1
2015-12-21Enable checked builds of CoreCLR.Eugene Rozenfeld1-1/+2
In checked builds coreclr, mscorlib, and the test are built optimized but assertion checking is on. This adds additional coverage (the jit is optimizing and assertion checking is on), speeds up testing compared to debug, and allows testing JIT stress modes. This doesn't affect CoreFX. Several tests are currently failing in checked configuration due to newly discovered bugs (JIT asserts). We didn't see these asserts in debug mode because by default JIT is in minopt mode; we didn't see these bugs in release mode because assertion checking is off. I will file the bugs once checked build changes are in.
2015-11-24Update xunit version to 2.1.0Jan Kotas1-3/+3
2015-11-18A few fixes for standlone Jit buildKyungwoo Lee1-0/+2
1. Fix for assertion in fgAddFieldSeqForZeroOffset The fix relaxed the assertion under FEATURE_REF_ZERO_OFFSET_ALLOWED. The feature is enabled when the standalone jit is built. 2. Package spec files for Windows/Linux and redirection. 3. Rename ProtoJit to RyuJit
2015-10-13Using DotNetCore version of BclRewriter in mscorlib buildJose Perez Rodriguez1-1/+4
2015-08-18Update buildtools version to 00079Jan Kotas1-1/+1
Required by VS2015
2015-08-17Build mscolrib.dll on UnixMatt Ellis1-2/+10
Initial work to get mscorlib.dll building via Roslyn + MSBuild running on top of Mono on Linux. - Use a newer version of BclRewriter.exe which works cross-platform, the major difference here is that now we need to specify the input assembly as a named argument instead (since fully qualified paths on Unix look like flags on Windows). - The ResGen we use comes from Mono, which does not support the -d flag, so we need to stop passing defines to ResGen. I know the mono folks recently did some work to address this, but long term we need to move towards getting our ResGen.exe running on CoreCLR and use that instead. - Don't require that mono is installed in order to build coreclr. If mono is not on the path, skip the build step to enable folks to do development without Mono. In this case, they will need to continue to build mscorlib.dll on Windows, targeting Unix. - Mono stability has been an issue for folks that have buddy tested this. I've found that recent mono 4.2 builds, when run with the Boehm GC work well for me. Other folks have other builds they like instead. The `skipmscorlib` flag can be passed to build.sh if you want to skip building mscorlib.dll locally.
2015-07-09Move CoreCLR to the modern build tools and dnxMatt Mitchell1-37/+68
This changes moves coreclr onto DNX (same version as corefx). Theoretically, this should allow these tests to target the desktop CLR. All of the old package.config files are gone and replaced with corresponding project.json files. The up front restore behavior is retained. Tests are now buildable individually, though not runnable in a similar fashion.
2015-06-07build,freebsd: Adds freebsdmscorlib to build.cmd.Peter Jas1-3/+4
2015-05-20Update Microsoft.DotNet.BuildTools.CoreCLR to version 1.0.2.Alex Ghiondea1-1/+1
This version updates BclRewriter.exe with a copy that can run on Dev15 RC
2015-04-20Xplat build changesVal Menn1-0/+1
Move the path of the global packages.config into a separate property. This allows xplat MSBuild to detect the path and adjust for non-Win systems. Addtionally, trim backslash as it escapes quotes on Linux
2015-03-31Change paths and os names to match corefxMatt Mitchell1-1/+9
* binaries is now bin, intermediates is now obj * modifying unixmscorlib build to instead be linuxmscorlib + osxmscorlib. * Change OS=Unix to OS=Linux/OS=OSX and modified properties to mimic corefx's TargetsUnix.
2015-02-23Place binaries and intermediates in folders that include OSMatt Mitchell1-6/+11
Rework the output paths so that the OS may appear in them. This then follows the same form as corefx. This solves a number of problems: 1) When building unix mscorlib after the regular build, we would use the wrong intermediates for incremental. 2) When testing windows after building unix mscorlib we'd use the wrong outputs and fail. This change removes our cmake directory and moves cmake generated files into intermediates (under OS/arch paths) The reason is that the intermediates go under here when actually doing the build, and on unix based systems, we need to generate the cmake files for different builds into different directories for the purpose of preserving incremental builds. Change clean behavior Clean should simply delete the root binary. We also should not make assumptions about whether necessary directories are available when we begin to build and should create them every time if necessary. Create directories as needed.
2015-02-19Setup the CoreCLR repo to use the LocalPackagePublish mechanism.Alex Ghiondea1-6/+28
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
2015-02-09Provide defaults for the values that come from the build.cmd script.alexghiondea1-0/+20
2015-01-30Initial commit to populate CoreCLR repo dotnet-bot1-0/+36
[tfs-changeset: 1407945]