summaryrefslogtreecommitdiff
path: root/init-tools.cmd
AgeCommit message (Collapse)AuthorFilesLines
2019-11-11[release/3.1] Fix use of ilasm during test builds when using a 3.0 SDK (#27818)Juan Hoyos1-3/+6
* Add fix for restore of ilasm The restore logic in buildtools tried to use a netcoreapp2.1 TFM for Linux-musl. This ended up restoring Linux-x64 binaries which then broke the test build. This change works around this by saving a copy of the depproj that BuildTools used into the tree and restore it as a 3.0 app manually in init-tools on our side of the build. * Change to a 3.0 SDK for servicing
2019-06-06Fix initializing BuildTools when the Platform environment variable is set ↵Elinor Fung1-0/+4
(#24998) * Make build-test.cmd exit if init-tools.cmd fails * Clear Platform variable before initializing BuildTools
2019-05-30Remove BuildTools from product build (#24841)Elinor Fung1-4/+1
* Remove BuildTools imports from product build * Split scripts for installing dotnet vs BuildTools
2019-05-10Properly set the nuget cache for the repo (#24505)Aaron Robinson1-1/+1
* Properly set the nuget cache for the repo * Change coreclr NuGet package cache from "./packages" to "./.packages"
2019-03-01Use arcade's version of dotnet to build (#22755)Steve MacLean1-10/+9
* Use arcade dotnet * Add cmake_msbuild.cmd Move msbuild.cmd to cmake_msbuild.bat Document intent that this file is only used to resolve Windows cmake dependency on desktop msbuild.exe Remove one instance of msbuild.cmd * Fix inittools.cmd * Remove spurious setup_vs_tools.cmd calls
2018-10-16Add hack for arm64/x86 to skip build tools restore (#20390)Jarret Shook1-1/+5
* Add hack for arm64/x86 to skip build tools restore * Address pr feedback * Correct PROCESSOR_ARCHITEW6432 comparison
2018-10-11Do not restore or initialize buildtools for x86/arm64 (#20370)Jarret Shook1-7/+7
* Do not restore or initialize buildtools for x86/arm64 * Remove string to download cli correctly
2018-10-08Runtest.py on Windows Arm(64) (#20227)Jarret Shook1-0/+5
* Initial infrastructure work to get arm(64) runtest.cmd working * Add excludes and improve runtest.py 1) Adds a build_test_wrappers only to build-test.sh. 2) Adds arm64 windows excludes 3) Adds printlastresults to runtest.cmd 4) corrects runsequential in runtest.sh 5) Corrects SequentialRun in runtest.py 6) Minor improvements to printing test results and copying native test binaries * Address pr feedback * Add to issues targets for arm64 * Working Pri 0 testing. * Remove unecessary common msbuild arguments * add pri1 excludes * Remove common msbuild args * Fix silly python3 issue
2018-08-24Use runtest.py to run tests for all platforms (#19213)Jarret Shook1-1/+25
Change build-test.sh to always build the xunit wrappers. Before it would drop a token and check the existence of the token. Unify x64 linux/OSX/Windows excludes into one file, issues.targets. Includes different locations in the file which show where to put excludes. Remove all target specific aspects of issues.targets, all tests are excluded now via wildcard, this allows expanding to .cmd and .sh based on the built platform. Unify path separators to forward slash(/) in issues.targets to support both platforms Clean up issues.targets by removing long standing exclude tests, specifically tests that have been excluded due to missing features like rva_statics. Add DisableProjectBuild to tests which have been removed from issues.targets Conditionally add DisableProjectBuild to tests which have been marked as unsupported on unix. This is mostly a port of the unsupportedOnUnix.txt list. Instead of excluding the tests, unix will simply not build them. If tests are built on windows, they will be run but they will return pass, the test wrapper will check return instantly. All exclusions ported to issues.targets for linux targets. Expand runtest.py, this includes simple issues that made it past the original CR. In addition it adds more optional features to help with inner loop dev work such as: creating a repro folder under bin/repro/.. which sets up the env and calls the failing test. In addition a launch.json will now be created under bin/repro/.. which can be used to easily debug using vscode. More logging, such as printing failures, longest running tests ect. Initial excludes ported for arm64 windows Arm64 linux, armhf unix excludes and enables running runtest.sh for these targets. arm64 windows and arm32 windows excludes and enables running runtest.cmd on arm64 targets init-tools.sh changes to pull armhf and aarch64 dotnetcli init-tools.cmd changes to pull x86 packages for dotnetcli for arm64 windows runtest.cmd for almost all scenarios will call runtest.py runtest.sh for almsot all scenarios will call runtest.py Removes all logic for running tests using runtest.sh
2018-08-08Updating init-tools.cmd to pass through PACKAGES_DIRTanner Gooding1-8/+8
2018-03-28Sync init-tools scripts with what is in source-buildWes Haggard1-16/+15
2017-12-18Put ToolDir property back on restore commandChad Nedzlek1-2/+2
2017-11-22Ask buildtools to also restore ILAsm (#15103)Michal Strehovský1-1/+4
We should start with having this restored before we start using it to make sure that nobody has tools downloaded/initialized without ILAsm.
2017-10-30Align init-tools scripts with other source-build reposWes Haggard1-5/+13
2017-10-27Merge branch 'master' of https://github.com/dotnet/coreclrJacek Blaszczynski1-6/+6
2017-10-24Use new feed tasks package & auto-update versionwtgodbe1-2/+2
2017-10-24Cleanup VsDevCmd.bat usage and improve build system messages to ease diagnosticsJacek Blaszczynski1-8/+8
2017-10-10Proof-of-concept of using new Publish infra in coreclrwtgodbe1-4/+4
2017-10-10Update to 2.0 RTM CLI (#14396)Jose Perez Rodriguez1-1/+1
* Update to 2.0 RTM CLI * PR feedback
2017-07-13[CoreCLR] Display the contents of init-tools.log (#12795)Ravi Eda1-8/+13
* Update attribute-value in security build definition. * Display init-tools log. * Ensure execute permission is available.
2017-05-27Fix tool initialization detection (#11912)mikedn1-2/+6
init-tools.cmd attempts to create a file in a directory that doesn't exist. File creation fails and next time the script is run initialization will be performed again. That wastes a lot of time.
2017-05-16Update Coreclr to 2.0.0 buildtoolswtgodbe1-36/+21
2017-04-01Refactor dotnet download code in init-tools.cmd (#10527)Luis G1-1/+3
* Refactor dotnet download code in init-tools.cmd This addresses the improvements proposed in issue #10526. Includes the init-tools.cmd script refactor and a new script called dotnet-download.ps1 which includes the extracted code and logic * Code review feedback changes * Fix spacing
2017-01-06Update CLI to 1.0.0-preview2-1-003182, BuildTools to ↵Davis Goodin1-1/+1
1.0.27-prerelease-01205-03 (#8829) * Update CLI to 1.0.0-preview2-1-003182, BuildTools to 1.0.27-prerelease-01205-03 * Add BuildVersion.targets and required properties to test directory's dir.props
2016-10-17Change the name buildtools semaphore temporarilyJan Kotas1-1/+1
2016-10-13Update tests to netcoreapp1.1Jan Kotas1-1/+9
2016-10-07Standardize on _echo name (#7532)Vance Morrison1-1/+1
2016-09-20Upgrade CLI, buildtools for RTM shared framework. (#7045)Davis Goodin1-2/+2
2016-07-19Make coreclr buildable on 32bit Windows 10. (#6316)Jim Ma1-1/+1
Automatically determine the OS architecture(x86 or x64) and download the correct dev tool. Fix #6308
2016-05-27Adding commit hash to all built binaries.Jose Perez Rodriguez1-1/+1
2016-05-26Add retry logic when downloading the CLI from Azure blob storage.Joel Hendrix1-1/+1
Downloading from Azure can transiently fail for a number of reasons. Add some retry logic when downloading to avoid transient failures. For *nix variants add a retry value when using curl (wget retries by default).
2016-04-22Partly fix the build issue when path to git repository has spaces (for ↵Mikhail Pilin1-10/+10
example "d:\z z\coreclr"). (#4388) The same issue in "d:\z z\coreclr\Tools\versioning.targets"(288): $(IntermediateOutputPath) should be "$(IntermediateOutputPath.TrimEnd('\'))" and all other path should be quoted with " in this line.
2016-04-15Detect if powershell version is suitable for restoring build toolsAndy Ayers1-4/+11
Powershell v3 or higher is required to decompress the build tools bundle. Windows 7 typically has v2 installed. Detect earlier versions and fail with a pointer to the build prerequisites and a download link for an updated version. Also propagate failures out of init-tools.cmd. The last step of this is unchecked since the build tool init script can return nonzero status even on success. See #3510.
2016-04-03Remove ReadyToRun workaroundJan Kotas1-3/+0
2016-03-30Upgrade dotnet cli version.Davis Goodin1-2/+2
2016-03-02Upgrade CLI version and buildtools, and make build file changes.Davis Goodin1-1/+1
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-23Correctly cleaning up the ToolRuntime folder once a new version is requiredJose Perez Rodriguez1-0/+2
2016-01-29update version of buildtoolsRahul Kumar1-0/+76
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 23:56:09 +0000