vieter-v
/
v
2
0
Fork 0
Code Issues Pull Requests Releases Activity

README.md: no more hardcoded installation path

pull/567/head
Alex Medvednikov 2019-06-25 02:02:05 +02:00 committed by GitHub
parent 5a469c2e37
commit add0abe956
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
README.md
View File

@ -72,24 +72,19 @@ The rest of the directories are vlib modules: `builtin/` (strings, arrays, maps)
### Linux and macOS ### Linux and macOS
```bash ```bash
# ~/code directory has to be used (it's a temporary limitation) # You can clone V anywhere
git clone https://github.com/vlang/v ~/code/v git clone https://github.com/vlang/v
cd ~/code/v/compiler cd v/compiler
make make
# Or build without make: # Or build without make:
wget https://vlang.io/v.c # Download the V compiler's source translated to C wget https://vlang.io/v.c # Download the V compiler's source translated to C
cc -std=gnu11 -w -o vc v.c # Build it with Clang or GCC cc -std=gnu11 -w -o vc v.c # Build it with Clang or GCC
./vc -o v . && rm vc # Use the resulting V binary to build V from V source, delete the old compiler ./vc -o v . && rm vc # Use the resulting V binary to build V from V source, delete the old compiler
./v -o v . # Bootstrap the compiler (this will also do initial setup)
``` ```
That's it! Now you have a V executable at `~/code/v/compiler/v`. That's it! Now you have a V executable at `v/compiler/v`.
Bootstrap the compiler to make sure it works:
```
./v -o v .
```
You can create a symlink so that it's globally available: You can create a symlink so that it's globally available: