By default, Nitrile will detect the current platform and architecture and build
for this target.
--arch allows you to pretend to be a different target.
This is for example useful to build a 32-bit application on a 64-bit platform.
It can also be used to package libraries for entirely different targets (e.g., create an ARM distribution on an Intel machine) when there are no build steps, i.e. when packaging just involves collecting files.
Possible values of
any(when the architecture and bitwidth do not matter)
The following values can be used when the architecture matters but the bitwidth does not matter:
The following values can be used when the bitwidth matters but the architecture does not matter:
--local-dependency DEP PATH¶
This option is useful when developing multiple packages at once. For example,
you are fixing a bug in package
current for which some changes in a
dep are needed. You can then clone the repository for
elsewhere, and use
--local-dependency dep path/to/dep when running
nitrile build or
nitrile test in the current package.
PATH/nitrile.yml must exist. The dependencies of the current package and those
DEP are combined. The constraint solver is invoked to find a set of
packages from both the current package’s
nitrile-packages. Thus, for each dependency, one of these sources is used (in
descending order of preference):
- The current package
- A package specified with
- A package installed in either the current package’s
nitrile-packages, or in the
nitrile-packagesdir of a local dependency
--local-dependency uses special logic to resolve dependencies, it
cannot be used with
--verbose to see the sources used for all the dependencies.
For the time being
--local-dependency has an impact on include paths only.
It is not possible to use this option to point to a package from which an
exe is needed.
Build steps of local dependencies are not taken into account. If your changes
in the local dependencies require a
nitrile build cycle (for example, if
the dependency contains C sources to link with), you have to manually run
nitrile build in the directory of the dependency.
the package to use.
This is like
--arch, but allows you to specify a
platform rather than an architecture. Possible values of
any(when the platform does not matter)
Enables verbose output.