Hi,
Patch 1/2 checks for and returns early if a null pointer is supplied as
input, thus preventing a crash / undefined behavior while dereferencing
it in the code following.
Patch 2/2 sets the version to 'unknown' as required by meson
documentation.
Thanks!
Seedo Paul (2):
guess: return early if source string is null
external_program: use 'unknown' as fallback version
src/functions/external_program.c | 4 +++-
src/guess.c | 4 ++++
2 files changed, 7 insertions(+), 1 deletion(-)
base-commit: 20cafd21421d417b8964723b4c06cfa28d857814
--
2.45.1
[PATCH 1/2] guess: return early if source string is null
Hi,
Other unimplemented methods / options:
The main missing methods are `dependency()` and`extension_modules()`.
Except for two additional kwargs, `dependency()` takes the same kwargs
as the standard `dependency()` function and returns a `python_dependency`
(that exposes the same methods as `dep` object). `extension_modules()`
has more or less the same semantics as the function `shared_module()`.
Since both of these methods have considerable overlap with their existing
standard function counterparts, I am unsure how best to implement them.
Is it possible to "offload" part of a module to meson script? Any ideas
/ help welcome.
- `install_sources()`: this works mostly similiar to `install_data()`. I
will send a patch implementing this soon (mostly copy pasted from
`install_data()` implementation.)
- Global option `python.bytecompile` is accepted, but does nothing
currently.
- Additional kwargs for some methods.
Thanks!
Seedo
Re: [PATCH 2/2] external_program: use 'unknown' as fallback version
Great news, I'm happy the python module is coming along.
> Is it possible to "offload" part of a module to meson script?
Not currently, but this would probably be easy to implement. I'll think
about it.
Stone