use ReST style code-block syntax

This commit is contained in:
Yuichi Nishiwaki 2014-05-21 13:04:00 +09:00
parent 9d84c67570
commit 03302665e6
1 changed files with 6 additions and 5 deletions

View File

@ -21,16 +21,17 @@ Installation
- make `Makefile` - make `Makefile`
Change directory to `build` then run `cmake` to create Makefile. Once `Makefile` is generated you can run `make` command to build picrin. Change directory to `build` then run `cmake` to create Makefile. Once `Makefile` is generated you can run `make` command to build picrin::
$ cd build $ cd build
$ cmake .. $ cmake ..
Actually you don't necessarily need to move to `build` directory before running `cmake` (in that case `$ cmake .`), but I strongly recommend to follow above instruction. Actually you don't necessarily need to move to `build` directory before running `cmake` (in that case `$ cmake .`), but I strongly recommend to follow above instruction.
- build - build
A built executable binary will be under bin/ directory and shared libraries under lib/. A built executable binary will be under bin/ directory and shared libraries under lib/::
$ make $ make
@ -38,19 +39,19 @@ If you are building picrin on other systems than x86_64, PIC_NAN_BOXING flag is
- install - install
Just running `make install`, picrin library, headers, and runtime binary are install on your system, by default into `/usr/local` directory. You can change this value via ccmake. Just running `make install`, picrin library, headers, and runtime binary are install on your system, by default into `/usr/local` directory. You can change this value via ccmake::
$ make install $ make install
- run - run
Before installing picrin, you can try picrin without breaking any of your system. Simply directly run the binary `bin/picrin` from terminal, or you can use `make` to execute it like this. Before installing picrin, you can try picrin without breaking any of your system. Simply directly run the binary `bin/picrin` from terminal, or you can use `make` to execute it like this::
$ make run $ make run
- debug run - debug run
If you execute `cmake` with debug flag `-DCMAKE_BUILD_TYPE=Debug`, it builds the binary with all debug flags enabled (PIC_GC_STRESS, VM_DEBUG, DEBUG). If you execute `cmake` with debug flag `-DCMAKE_BUILD_TYPE=Debug`, it builds the binary with all debug flags enabled (PIC_GC_STRESS, VM_DEBUG, DEBUG)::
$ cmake -DCMAKE_BUILD_TYPE=Debug .. $ cmake -DCMAKE_BUILD_TYPE=Debug ..