readmeL removed some spaces

pull/2596/head
JayatiGoyal 2019-10-31 17:10:17 +05:30 committed by Alexander Medvednikov
parent 0c229aacdd
commit 07ad60b89b
1 changed files with 1 additions and 10 deletions

View File

@ -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
```bash
git clone https://github.com/vlang/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`.)
V is being constantly updated. To update V, simply run
V is being constantly updated. To update V, simply run:
```
v up
```
### 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.
@ -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)
### Symlinking
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
```
### Docker
```bash
@ -86,8 +82,6 @@ docker run --rm -it vlang:latest
v
```
### Testing and running the examples
Make sure V can compile itself:
@ -106,7 +100,6 @@ hello world
>>>
```
```bash
cd examples
v hello_world.v && ./hello_world # or simply
@ -174,5 +167,3 @@ Code structure:
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.