VSadov/Satori
1
0
Fork 0
mirror of https://github.com/VSadov/Satori.git synced 2025-06-10 01:50:53 +09:00
Code Activity

Add docs link to editing-and-debugging (#41636)

Browse source 
We were missing a link to the Editing and Debugging doc from the main workflow doc.
This commit is contained in:
Andy Gocke 2020-08-31 15:42:51 -07:00 • committed by GitHub
parent 731eaf3545
commit 347be9ce2a
Signed by: github
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/workflow/README.md
View file

@ -40,6 +40,10 @@ On Unix like systems, arguments can be passed in with a single `-` or double hyp
The repository currently consists of different major parts: the runtimes, the libraries, and the installer.
To build just one part you use the root build script (build.cmd/sh), and you add the `-subset` flag.
## Editing and Debugging
For instructions on how to edit code and debug your changes, see [Editing and Debugging](editing-and-debugging.md).
## Configurations
You may need to build the tree in a combination of configurations. This section explains why.

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

@ -31,7 +31,7 @@ what are in the repository. In particular
Thus opening one of these two 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 'bin' directory. This is because it is created as part of the build.
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.
* See [Debugging CoreCLR](debugging/coreclr/debugging.md)