Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/mono/corert.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2017-10-04Delete VS2015 support (#4660)Jan Kotas
2017-10-03Prefer VS2015 for now to fix CI (#4642)Jan Kotas
2017-09-30Add placeholder build option for WebAssembly (#4620)Phill
* Add placeholder build option for WebAssembly * Add Emscripten build commands * Use Nmake in place of Make
2017-09-24Enable x86 build (#4598)Adeel Mujahid
2017-09-21Modernize RID detection in buildvars-setup.sh (#4588)Adeel Mujahid
2017-08-18Check for Visual C++ in buildvars-setup.cmd (#4343)Jan Kotas
2017-08-18Update VS2017 detection logic to match corefx (#4341)Jan Kotas
Manually running "Developer Command Prompt for VS 2017" is no longer necessary.
2017-07-12Tizen arm: refactoring of downloading build archives (#4145)Petr Bred
- a timestamp has been added to avoid downloading the same thing all the time Signed-off-by: Petr Bred <bredpetr@gmail.com>
2017-07-10Fix arm build (#4125)Petr Bred
Signed-off-by: Petr Bred <bredpetr@gmail.com>
2017-07-07Fix "build.cmd clean" (#4095)Jan Kotas
Fixes #4090
2017-06-27Fix rough edges after CLI update (#3983)Jan Kotas
* Move build-restore.cmd back to build-managed buildpipeline needs to be updated to make this split * Cleanup dir.props/dir.targets * Add back VS clues * Reformat whitespaces to match VS convention
2017-06-24Update CoreRT build to use latest .NET CLI and build tools (#3916)Jan Kotas
- Pick up latest .NET Core 2.0 CLI and buildtools - Remove all project.json references and convert everything to msbuild projects - Stick to vanilla .NET CLI project shape as much as possible. Minimize dependencies on buildtools special behaviors
2017-06-17Delete ToolsVersion attribute from msbuild filesJan Kotas
The latest project templates do not have it, and it is only good for generating warnings like the following in the detailed build log: Project file contains ToolsVersion="4.0". This toolset may be unknown or missing, in which case you may be able to resolve this by installing the appropriate version of MSBuild, or the build may have been forced to a particular ToolsVersion for policy reasons. Treating the project as if it had ToolsVersion="14.0". For more information, please see http://go.microsoft.com/fwlink/?LinkId=293424. [tfs-changeset: 1662024]
2017-05-31Fix for armel tizen (#3750)sergey ignatov
2017-04-27Add full support for building with VS 2017 (#3436)Michal Strehovský
This is a followup to #2390 that fixes a few things: * vs2017 no longer needs to be passed to build.cmd (it will be autodetected) * Building and running tests now works * Documentation updates to point out running from Developer Command prompt is needed. Fixes #3394.
2017-04-18[cross unix arm] Fixed issue #3320 (#3354)sergey ignatov
2017-04-17[cross unix arm] fix for #3323 (#3349)sergey ignatov
2017-02-25Linux support for multi-module (#2807)Simon Nattress
* Linux support for multi-module * Alter build integration scripts to support different naming / tool invocations on Linux. * Add GC / frame info for ELF to the same group as its associated method so it gets Comdat folded properly. * Add -multimodule switch to runtest.sh to run tests against a shared pre-compiled framework library. * Update ObjectWriter Nuget package which brings changes need to support Elf Comdat sections.
2017-02-14Fixes for cross building corert tests for arm architectures on Linux (#2682)sergey ignatov
2017-02-06Added armel buildingSergey Ignatov
2017-01-19Fix Unix thread shutdownJan Vorlicek
There was a problem with the secondary thread shutdown on Unix. First, when the TlsObjectDestructor is called, it is passed the key that was set using the pthread_setspecific before. But I was missing the fact that before the TlsObjectDestructor is called, the key is set to NULL. So we cannot use pthread_getspecific to get the key anymore and we can only use the value passed as the TlsObjectDestructor parameter. The second part of the problem was that the at the time the TlsObjectDestructor is called, the tls_CurrentThread to which the key points was already removed from the TLS and so an attempt to access tls_CurrentThread results in creation of a fresh new tls_CurrentThread. And our checks that we have at a few places that verify that the argument passed to the TlsObjectDestructor was actually the current thread pointer cannot be done. The fix is to use __cxa_thread_atexit to register a destruction callback for the ThreadStore object and use it instead of the pthread callback functionality.
2017-01-19Merge pull request #2534 from janvorli/update-default-clang-versionJan Vorlicek
Update default clang version to 3.9 and require xcode 8
2017-01-18Update default clang version to 3.9 and require xcode 8Jan Vorlicek
This change updates the default clang version used to build CoreRT to the latest stable version 3.9. It also removes the version 3.5 from the supported ones. The 3.5 has a bug preventing us from using thread_local C++ feature. Due to the same reason, the minimum supported xcode version on OSX is 8, so the prerequisities document is updated accordingly.
2017-01-18Split pipeline build to match CoreFX's model. (#2505)Chris Rummel
* Split pipeline build to match CoreFX's model. - OS-specific legs no longer publish to MyGet, they just upload to Azure. - New publish leg downloads from Azure and publishes to MyGet. - Only includes Microsoft.TargetingPack.Private.CoreRT for now, will add ILCompiler after we sort out what OS-specific packages should be named. * Addressing code review feedback (PR#2505).
2016-12-23Enable build with Visual Studio 2017 (#2390)William Kent
* Add support for VS2017 in buildvars-setup.cmd * Add support for VS2017 in gen-buildsys-win.cmd * VS2017 rearranges some files, update build-native.cmd to match * Update minimum CMake version to 3.7.0 This version is the first version that supports generating a project using the Visual Studio 2017 toolchain. * Fix bug in gen-buildsys-win.bat The code previously assumed that the probe-win.ps1 script is located in the current working directory. During my testing, I found that this is not robust enough for all use-cases. Using %~dp0 to identify the directory containing the batch file is more robust against this issue. * Use the correct copy of MSBuild to build the C++ projects Only the copy of MSBuild shipped with VS2017 can successfully build VS2017 vcxproj files. Using any other copy will cause strange errors. * Update documentation * Use "rem" for comments instead of "::" The Windows batch file interpreter treats these two symbols differently. When "::" is used within an if block, it can create spurious drive-not-found errors. Using "rem" avoids this problem.
2016-12-20Add packaging build changes and scripts. (#2325)Chris Rummel
2016-12-19Fix name of the RSP file for repro project (#2382)Michal Strehovský
RSP file got renamed in #2373 which broke the hackery to generate RSP files for the repro projects.
2016-12-17Use ExecutionPolicy ByPass to execute probe-win.ps1 script during the build ↵Jan Kotas
(#2379) Fixes #2377
2016-12-08Split build scripts for CI (#2309)Chris Rummel
In order to sign and package our builds properly in CI we need to split the build phases up. These changes add build-native, build-managed, and build-tests scripts, with build-packages soon to come. Summary: - Variable handling moved to buildvars-setup scripts to avoid duplication. - Everything else is from the old scripts with some path cleanup changes. - Build.cmd/sh now calls into the split scripts. - Updated build pipeline definitions for new scripts.