Document the binDir and nimble build changes.
This commit is contained in:
parent
70f03b2c9b
commit
6b007e8809
2 changed files with 9 additions and 2 deletions
|
|
@ -212,6 +212,9 @@ their own packages to it! Take a look at
|
|||
* ``srcDir`` - Specifies the directory which contains the .nim source files.
|
||||
**Default**: The directory in which the .nimble file resides; i.e. root dir of
|
||||
package.
|
||||
* ``buildDir`` - Specifies the directory which contains the .nim source files.
|
||||
**Default**: The directory in which the .nimble file resides; i.e. root dir of
|
||||
package.
|
||||
* ``bin`` - A list of files which should be built separated by commas with
|
||||
no file extension required. This option turns your package into a *binary
|
||||
package*, nimble will build the files specified and install them appropriately.
|
||||
|
|
|
|||
|
|
@ -158,8 +158,12 @@ Similar to the ``install`` command you can specify a version range, for example:
|
|||
### nimble build
|
||||
|
||||
The ``build`` command is mostly used by developers who want to test building
|
||||
their ``.nimble`` package. The ``install`` command calls ``build`` implicitly,
|
||||
so there is rarely any reason to use this command directly.
|
||||
their ``.nimble`` package. This command will build the package in debug mode,
|
||||
without installing anything. The ``install`` command will build the package
|
||||
in release mode instead.
|
||||
|
||||
If you are a developer willing to produce new Nimble packages please read the
|
||||
[developers.markdown file](developers.markdown) for detailed information.
|
||||
|
||||
### nimble list
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue