jyapayne/Nim
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update nims.rst to reflect that -d:release is now allowed in config.nims (#18221)

Browse source 
`-d:release` and `-d:danger` started working in `config.nims` after df429fa287 .
This commit is contained in:
Kaushal Modi 2021-06-10 08:29:03 -04:00 • committed by GitHub
commit 3481ff6172
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

12
doc/nims.rst
View file

@ -121,8 +121,8 @@ Here are few examples of using the `switch` proc:
.. code-block:: nim .. code-block:: nim
# command-line: --opt:size # command-line: --opt:size
switch("opt", "size") switch("opt", "size")
# command-line: --define:foo or -d:foo # command-line: --define:release or -d:release
switch("define", "foo") switch("define", "release")
# command-line: --forceBuild # command-line: --forceBuild
switch("forceBuild") switch("forceBuild")
@ -132,13 +132,13 @@ above example can be rewritten as:
.. code-block:: nim .. code-block:: nim
--opt:size --opt:size
--define:foo --define:release
--forceBuild --forceBuild
**Note**: In general, the *define* switches can also be set in **Note**: In general, the *define* switches can also be set in
NimScripts using `switch` or `--`, as shown in above NimScripts using `switch` or `--`, as shown in above examples. Few
examples. Only the `release` define (`-d:release`:option:) cannot be set `define` switches such as `-d:strip`:option:, `-d:lto`:option: and
in NimScripts. `-d:lto_incremental`:option: cannot be set in NimScripts.
NimScript as a build tool NimScript as a build tool