| Age | Commit message (Collapse) | Author |
|---|
|
After this option folks can do the following:
- Build all System.Collections projects
build.cmd/sh System.Collections
- Build System.Collection test projects (also runs tests)
build.cmd/sh src/System.Collections/tests
- While in a library directory build it all projects under it.
cd src\System.Collections
build.cmd/sh .
These also support any of the standard build options like framework,
flavor, os, allconfigurations, etc. Same rules apply that you have to
have built the entire tree for that configuration before this will
succeed.
|
|
Fixes https://github.com/dotnet/corefx/issues/14940
|
|
(#12475)
|
|
Changes to dev workflow scripts to use run command tool.
|
|
Adds the option to build an arm64 clrcompression using the build-native script. Also adds packages for the ARM64 build of clrcompression and sni - the latter of which is still built internally.
|
|
msbuild.log. These are useful as they will contain only errors and only warnings, respectively.
|
|
|
|
Update BuildTools
|
|
Echo is unconditionally turned off in batch files making it hard to debug
issues. This change provides a way to leave echo on by setting the _echo
environment var to on.
|
|
dotnet/wcf tries to keep their build scripts in line with what we have
in coreclr, but they don't have any native components to build. Gate our
native build on the existence of native build stuff.
Fixes #7001
|
|
Adds a logger to detect multiple projects building the same output path
with different global properties. This helps keep the build clean from
race conditions and redundant builds.
|
|
Currently the native Windows build will run whenever build.cmd is called. This commit adds a toggle to run only the native or managed component. By default both are built.
To build just the native components: ./build.cmd native
To build just the managed components: ./build.cmd managed
To build both: ./build.cmd
|
|
Adds Clean.cmd and Sync.cmd
There is also an option added for disabling batch restore of packages
during the build. Right now it restore is still enabled by default
but eventually it will be disabled and restore will only happen when
you call sync.cmd or build an individual project.
To disable batch restoring during build people can do one of 2 things:
1) set RestoreDuringBuild=false in your enviroment
2) pass /p:RestoreDuringBuild=false to build.cmd
|
|
Move init-tools to the top of build.cmd
Clean-up init-tools.cmd script and put most stuff out into a log file
Update build.cmd to add timestamp during logging also add timestamps
around the batch restore target so we can see how log it takes.
Adds the Summary option which will dump all the warnings and errors
at the end of the console output so the are more noticable.
Also cleans out the unnecessary restoring of packages.config files as we
no longer have any of those.
|
|
Merge changes from TFS
|
|
[tfs-changeset: 1562939]
|
|
|
|
[tfs-changeset: 1562317]
|
|
Unset `%Platform%`, so build don't get disrupted by the incorrect value
set in evn variable.
Fixes #69.
|
|
|
|
We were logging about 300 MB per incremental build and
the IO had a very noticeable impact on build time.
To get a diag log wen you actually need one:
build.cmd /flp:v=diag
|
|
|
|
Previouly, build.cmd had to be run from a "Developer Command Prompt"
window in order to find msbuild. This change removes that
requirement. If you are not in a Developer Command Promprt, we try to
load one for VS 2015 or VS 2013 (in that order) for the invocation of
build.cmd
|
|
- Set name of build log file and build project file into env variable so
they are more easily discoverable in the log foutput, and only defined
once.
- Fix minor typo in comments.
- This is equivalent change to PR dotnet/buildtools#71 applied here as
suggested by @weshaggard https://github.com/dotnet/buildtools/pull/71
|
|
|
|
Check for either VS 2013 or VS 2015 developer command prompt
and use whatever msbuild.exe they provide. The probing logic
before would prefer msbuild 12 over 14 even in a VS 2015
environment. This was confusing and meant different process
andresults between build and msbuild in a VS 2015 command
prompt on a machine with both versions of VS installed.
|
|
|
|
|
|
Since we are running msbuild with minimal verbosity there is not
summary output to the console at the end. This change pulls the
summary output from the log file and displays it. Something like:
0 Warning(s)
0 Error(s)
Time Elapsed 00:02:02.23
|
|
|
|
on the dotnet/corefx wiki.
|
|
|
|
Previously our repositories would build in either a Dev12 or a Dev14
Developer Command Prompt, but only if Dev12 (for MSBuild 12) was
on the box due to a hard-coded path to MSBuild 12. This change
will use MSBuild 14 if MSBuild 12 is not available. Also previously
this would look for MSBuild in the WOW Program Files path, this change
causes us to also look in the normal Program Files path for x86
Windows.
|
|
_ _ _____ _____ ____ _ _
| \ | | ____|_ _| | _ \ ___ ___| | _____| |
| \| | _| | | | |_) / _ \ / __| |/ / __| |
_| |\ | |___ | | | _ < (_) | (__| <\__ \_|
(_)_| \_|_____| |_| |_| \_\___/ \___|_|\_\___(_)
|
