Age | Commit message (Collapse) | Author | Files | Lines |
|
initialized
|
|
* 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
|
|
* Remove BuildTools imports from product build
* Split scripts for installing dotnet vs BuildTools
|
|
* Properly set the nuget cache for the repo
* Change coreclr NuGet package cache from "./packages" to "./.packages"
|
|
* 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
|
|
* fixes to build properly on FreeBSD
* remove ulimit from freebsd branch
|
|
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
|
|
|
|
|
|
The alpine 3.6 builds have been replaced with the more generic
linux-musl builds so removing them.
|
|
|
|
Add $DotNetBootstrapCliTarPath
Disable ILAsm nuget fetch while bootstrapping
|
|
* Building non-Windows builds using the CLI's MSBuild
|
|
|
|
We should start with having this restored before we start using it to make sure that nobody has tools downloaded/initialized without ILAsm.
|
|
|
|
Also did some small clean-up:
Fix missing tag from bad merge
Fix spacing in init-tools.sh
|
|
|
|
|
|
|
|
* Update to 2.0 RTM CLI
* PR feedback
|
|
This change enables full end to end build of coreclr including
managed code on Alpine Linux.
|
|
* Enable RedHat 6 in coreclr master
Enable RedHat 6 in coreclr master.
This is identical as the approved PR to enable RedHat 6 in coreclr
release/2.0.0:
https://github.com/dotnet/coreclr/pull/13301
* Correct Rid to match /src/.nuget/dirs.props
Correct Rid to match /src/.nuget/dirs.props
* Update dockertag and add logic to detect RHEL6 in init-tools.sh
Update dockertag and add logic to detect RHEL6 in init-tools.sh
* Port changes from Release/2.0.0 to fix coreclr RHEL 6 official runs.
Port changes from Release/2.0.0 to fix coreclr RHEL 6 official runs.
* Remove empty quotes.
Remove empty quotes.
|
|
|
|
* Update attribute-value in security build definition.
* Display init-tools log.
* Ensure execute permission is available.
|
|
|
|
|
|
|
|
|
|
* remove fedora 23
* Fedora rename
|
|
|
|
This is in line with how the `dotnet` tooling works.
|
|
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
|
|
|
|
GNU which might not be installed on a minimal GNU/Linux installation.
Refs #6994 and #7025.
|
|
This change allows init-tools to function in an "offline" mode where
tools are picked up from standalone folders. Specifically, it introduces
support for two new environment variables:
- DOTNET_TOOLSET_DIR
- BUILD_TOOLS_TOOLSET_DIR
If either is set, instead of downloading toolsets, we copy an already
existing one from the folder. The TOOLSET_DIR is a folder with sub
directories for every version of the tool in question.
For buildtools, we expect a published toolset (sans the "dotnetcli"
folder) not just a set of nuget packages (i.e. the layout of Tools/
after running ./init-tools.sh in "online" mode).
The above varibles are useful for situations where we want to carry
multiple toolsets with us, but are less helpful for places where a
developer has produced their own toolset by hand (since the resulting
folder structure contains extra version information). For these cases,
I've added
- DOTNET_TOOL_DIR
- BUILD_TOOLS_TOOL_DIR
Which work like the above but don't require the nested folder structure.
|
|
|
|
|
|
|
|
|
|
* Use hash instead of which in build.sh
* Use hash instead of which in init-tools.sh.
* Use hash instead of which in gen-buildsys-clang.sh.
|
|
|
|
/init-tools.sh:72 tries to compare strings like this:
if [ "$OS"=="OSX" ]; then
What it actually does is different to what it looks like:
$ echo $OS
$ if [ "$OS"=="OSX" ]; then echo EQUAL; fi
EQUAL
$ if [ "$OS" == "OSX" ]; then echo EQUAL; fi
$
This commit fixes the typo and makes OSX workaround run on macs only.
|
|
With the updated buildtools, we should now be able to build on all the supported distros:
- Centos 7
- Fedora 23
- openSUSE 13.2
- RHEL 7.2
- Ubuntu 14.04
- Ubuntu 16.06
I also cleaned up how we compute the RID for the tools to restore.
|
|
There were two issues:
- $__BuildArch is not defined in init-tools.sh, so we would always
download the ubuntu version of the CLI, since our check for
`rhel.7.2-x64` would never fire.
- There was a small RHEL specific bug in BuildTools itself that
manifested when we actually were able to download the CLI and try to
restore the runtime.
|
|
|
|
- Add packages for Fedora 23 and OpenSuse 13.2
- Move the package authoring for Ubuntu into versioned folders
- Update our selection logic for what to produce to be based on an
actual RID instead of just a distro name, since that's now not enough
with us building for two Ubuntu versions
|
|
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).
|
|
into init-tools.sh
|
|
|