Age | Commit message (Collapse) | Author | Files | Lines |
|
the simple_version still goes through the big version of this function,
but at last we have type checking
|
|
This has never been in permittedKwargs, it does nothing, and it was
never documented, so it seems pretty safe to just remove it.
|
|
All other CI images already seed it explicitly.
|
|
|
|
|
|
|
|
This will avoid false positives with the ARM Ltd. `armclang` compiler.
|
|
|
|
We really don't want to be mutating global state, so let mypy yell at us
when we try.
|
|
Add ability to mutate a target's `extra_files` list through the
rewriter.
The logic is copied from sources add/rm, but changes the `extra_files`
kwarg instead of the sources positional argument.
Has additional logic to handle creating the `extra_files` list if it
doesn't exist.
|
|
In 1fb6c939473ca7cdab2 the intl dep gained support for static linking
which also forwarded this property to the iconv sub dependency.
The refactoring in 214d03568f75 lost this change, which results in
iconv getting linked dynamically again.
Forward static again to fix this.
|
|
Fix regressions caused by typing changes
|
|
Even if we install without a DESTDIR set, we should never update
ldconfig when cross compiling.
Fixes #9707
|
|
|
|
Which needs to be converted from None to an empty list
|
|
These are actually just flags, they don't take any arguments (except
prefix, which was already handled correctly), and as such their
arguments should be booleans, not strings, and they should default to
False.
|
|
Which is what it should have been all along.
|
|
|
|
We were missing the most important keyword argument of them all!
|
|
Currently there is a try/except around the function that detects and
rejects this, which instead of rejecting it, spawns a warning and
continue.
This warning exists because of 'test cases/vala/9 gir/' which passes a
vala generated output that isn't a return value (!!!) using string
joining with the meson.current_build_dir() function (also !!!) because
we officially document this (!!! for a third time) as the only way to
make a vala shared library generate a typelib with a custom_command from
the automatically generated gir:
https://mesonbuild.com/Vala.html#gobject-introspection-and-language-bindings
In #3061 we converted strings to Files, but only if none of them were
this vala hack. Due to the precise implementation, we also failed to
convert strings to Files if any other error occurred, but since we only
want to ignore errors for generated vala outputs, tighten that check and
specifically call out generated files in the warning.
Fixes #8635
|
|
|
|
Using the deprected_message helper.
|
|
There is a change here, in that packages has error messaging for using
IncludeDirs objects in the packages argument, but it never worked, so
the message was useless.
|
|
|
|
There are thee arguments that are passed directly to CustomTarget which
are not in the permittedKwargs: depends, depend_files, and build_always.
The first two are obviously generically useful, as they allow creating
correct ordering. The latter, not so much. Since it was an error to pass
it, we'll just delete it.
|
|
|
|
module
These are going to be used in the gnome module.
|
|
Use a proper install option for this. Now `install_<type>` can directly
override `install` instead of passing a boolean to the string kwarg
`install_dir_<type>`.
|
|
*_typelib
generate_gir forces building both the typelib and gir, and some people
only want one or the other (probably only the typelib?) which means
flagging the other as install_dir: false in the same way custom_target
supports.
As this always worked, albeit undocumented, make sure it keeps working.
It's pretty reasonable to allow, anyway.
Fixes https://github.com/mesonbuild/meson/pull/9484#issuecomment-980131791
|
|
|
|
This allows these two arguments to take a tuple of (version, message),
where the message will be passed to Feature*'s message parameter
|
|
|
|
For passing an extra message to Feature*
This allows providing a more detailed message.
|
|
This just makes things a little cleaner, and allows more accurate error
reporting.
|
|
Which shouldn't be Dict[str, str], they should be Dict[_T, str], as nay
value that can be passed to types is valid here.
|
|
Which lets pytest understand unittest.subtest
|
|
This has been removed as an explicit package in impish. It seems that
having pkg-config installed and adding arm as an arch will cause it to
be generated automatically
|
|
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
|
|
Fixes: #8333
|
|
Fixes: #7585
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
|
|
Meson was passing only the first output and warning about it. To do this
easily, refactor construct_target_rel_path to return a list.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
|
|
compile_moc accepts "dependencies" for the same reason preprocess does,
but the original documentation never copied this over from the
preprocess docs.
See: https://github.com/mesonbuild/meson/issues/9683#issuecomment-986825041
|
|
Re-use any already determined rpaths for a target.
Fixes #9695
|
|
|
|
I don't understand the purpose of this confusing API naming split.
|
|
FeatureCheck always immediately sets extra_message to '' if it isn't
explicitly passed, so there is really no point in using None as a
sentinel that is never used.
Names used in init functions are sometimes pointlessly different from
the class instance attributes they are immediately assigned to. They
would make more sense if defined properly.
|
|
Originally name should have been set to required=True, but since then
the requirement to name CustomTargets (which compile_resources is a
wrapper around) has been dropped. As such we just need to allow the
default value of None through.
Fixes: #9698
|
|
Make it possible to specify a wrapper for executing binaries
in cross-compiling scenarios.
(usually, some kind of target hardware emulator, such as qemu)
|
|
It was originally forgotten in merge_file() and later added for parity
with gettext(). This means that the FeatureNew for each function is
different.
|
|
If you use it, we emit a warning telling you to use LINGUAS instead. So
we should warn people in the documentation as well.
Fixes #9495
|