forked from PyO3/maturin
-
Notifications
You must be signed in to change notification settings - Fork 1
/
publish.stdout
160 lines (104 loc) · 4.94 KB
/
publish.stdout
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
Build and publish the crate as python packages to pypi
Usage: maturin[EXE] publish [OPTIONS] [ARGS]...
Arguments:
[ARGS]...
Rustc flags
Options:
--debug
Do not pass --release to cargo
--no-strip
Do not strip the library for minimum file size
--no-sdist
Don't build a source distribution
-r, --repository <REPOSITORY>
The repository (package index) to upload the package to. Should be a section in the config
file.
Can also be set via MATURIN_REPOSITORY environment variable.
[env: MATURIN_REPOSITORY=]
[default: pypi]
--repository-url <REPOSITORY_URL>
The URL of the registry where the wheels are uploaded to. This overrides --repository.
Can also be set via MATURIN_REPOSITORY_URL environment variable.
[env: MATURIN_REPOSITORY_URL=]
-u, --username <USERNAME>
Username for pypi or your custom registry.
Can also be set via MATURIN_USERNAME environment variable.
Set MATURIN_PYPI_TOKEN variable to use token-based authentication instead
[env: MATURIN_USERNAME=]
-p, --password <PASSWORD>
Password for pypi or your custom registry.
Can also be set via MATURIN_PASSWORD environment variable.
--skip-existing
Continue uploading files if one already exists. (Only valid when uploading to PyPI. Other
implementations may not support this.)
--non-interactive
Do not interactively prompt for username/password if the required credentials are missing.
Can also be set via MATURIN_NON_INTERACTIVE environment variable.
[env: MATURIN_NON_INTERACTIVE=]
--compatibility [<compatibility>...]
Control the platform tag on linux.
Options are `manylinux` tags (for example `manylinux2014`/`manylinux_2_24`) or `musllinux`
tags (for example `musllinux_1_2`) and `linux` for the native linux tag.
Note that `manylinux1` and `manylinux2010` is unsupported by the rust compiler. Wheels
with the native `linux` tag will be rejected by pypi, unless they are separately validated
by `auditwheel`.
The default is the lowest compatible `manylinux` tag, or plain `linux` if nothing matched
This option is ignored on all non-linux platforms
-i, --interpreter [<INTERPRETER>...]
The python versions to build wheels for, given as the executables of interpreters such as
`python3.9` or `/usr/bin/python3.8`
-f, --find-interpreter
Find interpreters from the host machine
-b, --bindings <BINDINGS>
Which kind of bindings to use
[possible values: pyo3, pyo3-ffi, rust-cpython, cffi, uniffi, bin]
-o, --out <OUT>
The directory to store the built wheels in. Defaults to a new "wheels" directory in the
project's target directory
--skip-auditwheel
Don't check for manylinux compliance
--zig
For manylinux targets, use zig to ensure compliance for the chosen manylinux version
Default to manylinux2014/manylinux_2_17 if you do not specify an `--compatibility`
Make sure you installed zig with `pip install maturin[zig]`
-q, --quiet
Do not print cargo log messages
-j, --jobs <N>
Number of parallel jobs, defaults to # of CPUs
--profile <PROFILE-NAME>
Build artifacts with the specified Cargo profile
-F, --features <FEATURES>
Space or comma separated list of features to activate
--all-features
Activate all available features
--no-default-features
Do not activate the `default` feature
--target <TRIPLE>
Build for the target triple
[env: CARGO_BUILD_TARGET=]
--target-dir <DIRECTORY>
Directory for all generated artifacts
-m, --manifest-path <PATH>
Path to Cargo.toml
--ignore-rust-version
Ignore `rust-version` specification in packages
-v, --verbose...
Use verbose output (-vv very verbose/build.rs output)
--color <WHEN>
Coloring: auto, always, never
--frozen
Require Cargo.lock and cache are up to date
--locked
Require Cargo.lock is up to date
--offline
Run without accessing the network
--config <KEY=VALUE>
Override a configuration value (unstable)
-Z <FLAG>
Unstable (nightly-only) flags to Cargo, see 'cargo -Z help' for details
--timings=<FMTS>
Timing output formats (unstable) (comma separated): html, json
--future-incompat-report
Outputs a future incompatibility report at the end of the build (unstable)
-h, --help
Print help (see a summary with '-h')