-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
config-settings support needs docs #230
Comments
Sounds like maybe the config-settings design is that the backend is responsible for taking a single (For comparison, meson setup |
I haven't found this documented any better than here https://peps.python.org/pep-0517/#config-settings where is only very vaguely defined. But this works with
thus I think the design is for the option to be repeated. But this brings the questions: why |
I missed that this existed and created #235 which has error logs. |
Closes mesonbuild#197, mesonbuild#230, mesonbuild#253, and mesonbuild#264 Sets us up to fix mesonbuild#138, mesonbuild#233, and mesonbuild#224 Signed-off-by: Filipe Laíns <lains@riseup.net>
Closes mesonbuild#197, mesonbuild#230, mesonbuild#253, and mesonbuild#264 Sets us up to fix mesonbuild#138, mesonbuild#233, and mesonbuild#224 Signed-off-by: Filipe Laíns <lains@riseup.net>
Closes mesonbuild#197, mesonbuild#230, mesonbuild#253, and mesonbuild#264 Sets us up to fix mesonbuild#138, mesonbuild#233, and mesonbuild#224 Signed-off-by: Filipe Laíns <lains@riseup.net>
Closes mesonbuild#197, mesonbuild#230, mesonbuild#253, and mesonbuild#264 Sets us up to fix mesonbuild#138, mesonbuild#233, and mesonbuild#224 Signed-off-by: Filipe Laíns <lains@riseup.net>
Closes mesonbuild#197, mesonbuild#230, mesonbuild#253, and mesonbuild#264 Sets us up to fix mesonbuild#138, mesonbuild#233, and mesonbuild#224 Signed-off-by: Filipe Laíns <lains@riseup.net>
Closes mesonbuild#197, mesonbuild#230, mesonbuild#253, and mesonbuild#264 Sets us up to fix mesonbuild#138, mesonbuild#233, and mesonbuild#224 Signed-off-by: Filipe Laíns <lains@riseup.net>
Closes mesonbuild#197, mesonbuild#230, mesonbuild#253, and mesonbuild#264 Sets us up to fix mesonbuild#138, mesonbuild#233, and mesonbuild#224 Signed-off-by: Filipe Laíns <lains@riseup.net>
Closes mesonbuild#197, mesonbuild#230, mesonbuild#253, and mesonbuild#264 Sets us up to fix mesonbuild#138, mesonbuild#233, and mesonbuild#224 Signed-off-by: Filipe Laíns <lains@riseup.net>
This is a follow-up issue for gh-167. The most important thing to add is docs. The invocations are verbose and argument quoting can be difficult, so we need a good number of one-liners as usage examples (there are some near the bottom of gh-167).
Also, it's possible that there's still an issue with functionality.
--config-settings
doesn't take multiple arguments at once, so if you'd want to pass multiple arguments tomeson setup
, it seems like there's no good way to do it. Something like:seems to just use one of the two arguments. @tacaswell and I tried for a while, and didn't get it to work. It's possible we missed something.
The text was updated successfully, but these errors were encountered: