readme: Fix 'mkdir -p' and symlink typo
You don't need to provide the ``-p`` flag which is used to create nested directories. Similarly, using ``$HOME`` for the symlink isn't strictly necessary, let's change that.pull/439/head
parent
64a5dc3f23
commit
f72de84e9c
|
@ -51,7 +51,7 @@ The rest of the directories are vlib modules: `builtin/` (strings, arrays, maps)
|
||||||
### Linux and macOS
|
### Linux and macOS
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
mkdir -p ~/code && cd ~/code # ~/code directory has to be used (it's a temporary limitation)
|
mkdir ~/code && cd ~/code # ~/code directory has to be used (it's a temporary limitation)
|
||||||
git clone https://github.com/vlang/v
|
git clone https://github.com/vlang/v
|
||||||
cd v/compiler
|
cd v/compiler
|
||||||
make
|
make
|
||||||
|
@ -68,7 +68,7 @@ That's it! Now you have a V executable at `~/code/v/compiler/v`.
|
||||||
You can create a symlink so that it's globally available:
|
You can create a symlink so that it's globally available:
|
||||||
|
|
||||||
```
|
```
|
||||||
sudo ln -s $HOME/code/v/compiler/v /usr/local/bin/v
|
sudo ln -s ~/code/v/compiler/v /usr/local/bin/v
|
||||||
```
|
```
|
||||||
|
|
||||||
### Windows
|
### Windows
|
||||||
|
|
Loading…
Reference in New Issue