readmeL removed some spaces
parent
0c229aacdd
commit
07ad60b89b
11
README.md
11
README.md
|
@ -38,7 +38,6 @@ V 1.0 release is planned for December 2019. Right now V is in an alpha stage.
|
||||||
|
|
||||||
### Linux, macOS, Windows, *BSD, Solaris, WSL, Android, Raspbian
|
### Linux, macOS, Windows, *BSD, Solaris, WSL, Android, Raspbian
|
||||||
|
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
git clone https://github.com/vlang/v
|
git clone https://github.com/vlang/v
|
||||||
cd v
|
cd v
|
||||||
|
@ -49,13 +48,12 @@ That's it! Now you have a V executable at `[path to V repo]/v`. `[path to V repo
|
||||||
|
|
||||||
(On Windows `make` means running `make.bat`, so make sure you use `cmd.exe`.)
|
(On Windows `make` means running `make.bat`, so make sure you use `cmd.exe`.)
|
||||||
|
|
||||||
V is being constantly updated. To update V, simply run
|
V is being constantly updated. To update V, simply run:
|
||||||
|
|
||||||
```
|
```
|
||||||
v up
|
v up
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
||||||
### C compiler
|
### C compiler
|
||||||
|
|
||||||
You'll need Clang or GCC or Visual Studio. If you are doing development, you most likely already have one of those installed.
|
You'll need Clang or GCC or Visual Studio. If you are doing development, you most likely already have one of those installed.
|
||||||
|
@ -66,7 +64,6 @@ Otherwise, follow these instructions:
|
||||||
|
|
||||||
[github.com/vlang/v/wiki/Installing-a-C-compiler-on-Windows](https://github.com/vlang/v/wiki/Installing-a-C-compiler-on-Windows)
|
[github.com/vlang/v/wiki/Installing-a-C-compiler-on-Windows](https://github.com/vlang/v/wiki/Installing-a-C-compiler-on-Windows)
|
||||||
|
|
||||||
|
|
||||||
### Symlinking
|
### Symlinking
|
||||||
|
|
||||||
You can create a `/usr/local/bin/v` symlink so that V is globally available:
|
You can create a `/usr/local/bin/v` symlink so that V is globally available:
|
||||||
|
@ -75,7 +72,6 @@ You can create a `/usr/local/bin/v` symlink so that V is globally available:
|
||||||
sudo ./v symlink
|
sudo ./v symlink
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
||||||
### Docker
|
### Docker
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
|
@ -86,8 +82,6 @@ docker run --rm -it vlang:latest
|
||||||
v
|
v
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Testing and running the examples
|
### Testing and running the examples
|
||||||
|
|
||||||
Make sure V can compile itself:
|
Make sure V can compile itself:
|
||||||
|
@ -106,7 +100,6 @@ hello world
|
||||||
>>>
|
>>>
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
cd examples
|
cd examples
|
||||||
v hello_world.v && ./hello_world # or simply
|
v hello_world.v && ./hello_world # or simply
|
||||||
|
@ -174,5 +167,3 @@ Code structure:
|
||||||
https://github.com/vlang/v/blob/master/CONTRIBUTING.md
|
https://github.com/vlang/v/blob/master/CONTRIBUTING.md
|
||||||
|
|
||||||
If you introduce a breaking change and rebuild V, you will no longer be able to use V to build itself. So it's a good idea to make a backup copy of a working compiler executable.
|
If you introduce a breaking change and rebuild V, you will no longer be able to use V to build itself. So it's a good idea to make a backup copy of a working compiler executable.
|
||||||
|
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue