VSadov/Satori
1
0
Fork 0
mirror of https://github.com/VSadov/Satori.git synced 2025-06-12 02:30:29 +09:00
Code Activity

Add configureonly option to host native build (#60889)

Browse source
This commit is contained in:
Elinor Fung 2021-10-26 20:28:48 -07:00 • committed by GitHub
parent ffa122aeab
commit 760a76bf4d
Signed by: github
GPG key ID: 4AEE18F83AFDEB23
5 changed files with 19 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/workflow/editing-and-debugging.md
View file

@ -27,12 +27,14 @@ The repository has a number of Visual Studio Solutions files (`*.sln`) that are
* `crossgen` - This is the host program that runs the JIT compiler and produces .NET Native images (`*.ni.dll`)
for C# code.
* This project can be automatically generated and opened in Visual Studio by running `./build.cmd -vs CoreCLR.sln -a <Arch> -c <BuildType>` from the root of the repository.
* `artifacts\obj\win-<Arch>.<BuildType>\corehost\ide\corehost.sln` - this solution contains the native (C++) projects for the [host components](../design/features/host-components)
* This project can be automatically generated and opened in Visual Studio by running `./build.cmd -vs corehost.sln -a <Arch> -c <BuildType>` from the root of the repository.
Thus opening one of these two solution files (double clicking on them in Explorer) is typically all you need
Thus opening one of these solution files (double clicking on them in Explorer) is typically all you need
to do most editing.
Notice that the CoreCLR solution is under the `artifacts` directory. This is because it is created as part of the build.
Thus you can only launch this solution after you have built at least once with the `-msbuild` flag or run the `./build.cmd -vs CoreCLR.sln` command line with the specified architecture and configuration.
Notice that the CoreCLR and corehost solutions are under the `artifacts` directory. This is because they are created as part of the build.
Thus you can only launch these solutions after you have built at least once with the `-msbuild` flag or run the `./build.cmd -vs CoreCLR.sln` or `./build.cmd -vs corehost.sln` command line with the specified architecture and configuration.
* See [Debugging CoreCLR](debugging/coreclr/debugging.md)