summaryrefslogtreecommitdiff
path: root/Documentation/building
diff options
context:
space:
mode:
authorArtem Koval <artem.koval@gmail.com>2018-05-18 08:28:37 +0300
committerDan Moseley <danmose@microsoft.com>2018-05-17 22:28:37 -0700
commitb12c344020ba4cc5bccff377c8922f5434aa293e (patch)
tree9d657a9196a2c5e66da0120d4e29a810e90bda94 /Documentation/building
parent2fb587937b1926d59f2fd8396196571e356fc596 (diff)
downloadcoreclr-b12c344020ba4cc5bccff377c8922f5434aa293e.tar.gz
coreclr-b12c344020ba4cc5bccff377c8922f5434aa293e.tar.bz2
coreclr-b12c344020ba4cc5bccff377c8922f5434aa293e.zip
Update osx-instructions.md (#18000)
When following this instruction CoreFX build won't happen until we change the folder to the CoreFX's one. In essence ./build.sh will trigger CoreCLR build once again. It may be a minor thing for an experienced user but can become a significant blocker for someone who's not that experienced with the command line and needs to compile CoreCLR. And it will diminish the awesomeness of .NET Core which we can't allow! The proposed change is just a directory change when inside the CoreCLR folder.
Diffstat (limited to 'Documentation/building')
-rw-r--r--Documentation/building/osx-instructions.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/Documentation/building/osx-instructions.md b/Documentation/building/osx-instructions.md
index dc01ae402a..eb077b179d 100644
--- a/Documentation/building/osx-instructions.md
+++ b/Documentation/building/osx-instructions.md
@@ -101,6 +101,7 @@ Build the Framework
===================
```sh
+dotnet-mbp:coreclr richlander$ cd ../corefx/
dotnet-mbp:corefx richlander$ ./build.sh
```