iskm/learnxinyminutes-docs
1
0
Fork 0
mirror of https://github.com/adambard/learnxinyminutes-docs.git synced 2024-12-23 17:41:41 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Uniform tics, noteable arguments addition.

Browse Source 
Changed all N-tics for preformatted/code text into single tics if that code was sinle line (i.e. bash commands, compiler arguments)
Added --main-module, --module-dir to Notable arguments section.
Realized that the text <blah blah> was disappering, so changed it to `<bla bla>`. Need to confirm it success.
This commit is contained in:
Ian Bertolacci 2015-08-02 15:44:16 -07:00
parent b27d526822
commit 27cc820762
1 changed files with 12 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
chapel.html.markdown
View File

@ -968,9 +968,8 @@ Occasionally check back here and on the [Chapel site](http://chapel.cray.com) to
### What this tutorial is lacking: ### What this tutorial is lacking:
* Modules and standard modules * Exposition of the standard modules
* Multiple Locales (distributed memory system) * Multiple Locales (distributed memory system)
* ```proc main(){ ... }```
* Records * Records
* Whole/sliced array assignment * Whole/sliced array assignment
* Range and domain slicing * Range and domain slicing
@ -994,26 +993,28 @@ Chapel can be built and installed on your average 'nix machine (and cygwin).
[Download the latest release version](https://github.com/chapel-lang/chapel/releases/) [Download the latest release version](https://github.com/chapel-lang/chapel/releases/)
and its as easy as and its as easy as
1. ```tar -xvf chapel-1.11.0.tar.gz``` 1. `tar -xvf chapel-1.11.0.tar.gz`
2. ```cd chapel-1.11.0``` 2. `cd chapel-1.11.0`
3. ```make``` 3. `make`
4. ```source util/setchplenv.bash # or .sh or .csh or .fish``` 4. `source util/setchplenv.bash # or .sh or .csh or .fish`
You will need to `source util/setchplenv.EXT` from within the Chapel directory (`$CHPL_HOME`) every time your terminal starts so its suggested that you drop that command in a script that will get executed on startup (like .bashrc). You will need to `source util/setchplenv.EXT` from within the Chapel directory (`$CHPL_HOME`) every time your terminal starts so its suggested that you drop that command in a script that will get executed on startup (like .bashrc).
Chapel is easily installed with Brew for OS X Chapel is easily installed with Brew for OS X
1. ```brew update``` 1. `brew update`
2. ```brew install chapel``` 2. `brew install chapel`
Compiling Code Compiling Code
-------------- --------------
Builds like other compilers: Builds like other compilers:
```chpl myFile.chpl -o myExe``` `chpl myFile.chpl -o myExe`
Notable arguments: Notable arguments:
* ``--fast``: enables a number of optimizations and disables array bounds checks. Should only enable when application is stable. * `--fast`: enables a number of optimizations and disables array bounds checks. Should only enable when application is stable.
* ```--set <Symbol Name>=<Value>```: set config param <Symbol Name> to <Value> at compile-time * `--set <Symbol Name>=<Value>`: set config param `<Symbol Name>` to `<Value>` at compile-time.
* `--main-module <Module Name>`: use the main() procedure found in the module `<Module Name>` as the executable's main.
* `--module-dir <Directory>`: includes `<Directory` in the module search path.