Ok, forgot my last mail. I read the mail wrong and also forgot NM's
requirement to build it on systems without python3.
Sorry,
El mar., 25 ago. 2020 a las 14:56, Iñigo Martínez ()
escribió:
> Although meson needs python 3 to work, meson's Python module[0] can be
> also used to w
Although meson needs python 3 to work, meson's Python module[0] can be also
used to work with python2 code.
BTW, I still have a couple of meson only (I mean, my changes were only
meson oriented) updates for NetworkManager around. These changes remove
autotools and also moves NM to the latest gette
Hi,
I can also provide some assistance regarding meson if necessary.
The first step would be to execute meson in the cloned NM repository
providing a build directory. Something like `meson _build`. If this step is
successful, you would then execute ninja to build it providing the
previously used
those that have modified the files,
this is the list of involved authors:
Antonio Cardace
Beniamino Galvani
Benjamin Berg
Christian Kellner
Corentin Noël
Francesco Giudici
Iñigo Martínez
Jan Alexander Steffens (heftig)
Jan Tojnar
Javier Arteaga
Lubomir Rintel
Michael Biebl
Soapux
Taegil Bae
Thomas
Hi,
What about meson build files? Although usually the license is not included,
there are some exceptions that they do[0].
If necessary, I also agree with relicensing.
BR,
[0] https://github.com/systemd/systemd/blob/master/meson.build
El jue., 9 ene. 2020 a las 15:40, Dan Williams via networkm
The following symbols are missing from the libnm-glib library:
* libnm_glib_get_network_state
* libnm_glib_init
* libnm_glib_register_callback
* libnm_glib_shutdown
* libnm_glib_unregister_callback
This has been changed by linking `libdeprecated_nm_glib` as a whole.
---
libnm-glib/meson.build |
The `settings-docs.c` file is generated by processing the
`nm-property-docs.xml` file. Although this works in autotools,
the `.c` extension makes meson not to handle it properly.
Given the fact that it only contains a number of defines it
makes sense to change its extension to `.h` an use it as a
There are some linker scripts which are used at link time. These
are not modified very much, so by using variables with already
formatted string can increase meson's parsing time.
Preformatted strings have been used for `binary`, `device` and
`settings` link scripts.
Those link scripts which are
The process for retrieving jansson's soname has been slightly
simplified.
---
meson.build | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meson.build b/meson.build
index 1a2d3b97b..ec283a96c 100644
--- a/meson.build
+++ b/meson.build
@@ -188,8 +188,7 @@ config_h.set10('WITH_J
Hi,
Although meson has some interesting benefits, it still has some
stilshortcomings compared to autotools.
While both build systems coexists, this patch adds meson build files as
autotools distributable files, so they are also packed when generating the
distributable file.
BR,
From 983ef983c84f
Some targets are missing dependencies on some generated sources in
the meson port. These makes the building fail due to missing source
files on a highly multithreaded building.
These dependencies have been resolved by taking advantage of meson's
internal dependencies and reviewing the whole meson
In a recent commit 686afe531ab3774cd818feda8361de74101971f5, a new
macro called `_NM_SD_MAX_CLIENT_ID_LEN` was introduced. However, the
systemd DHCP client handler did not include the file where the
macro was defined, `nm-types.h`. Although this worked in autotools,
it fails on meson.
The include
In a recent commit 1402fa7487b29fc1ea39a6bf7659fee7f30bb0e0 a new
way for testing Red Hat compatible distributions had been added.
This new testing approach has also been added to meson.
---
meson.build | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meson.build b/meson.buil
gtkdoc uses some custom generated targets as content files. However,
there are still two problem. The first is that gtkdoc does not
support targets which are not strings. This is being fixed in the
following issue:
https://github.com/mesonbuild/meson/pull/2806
The second issue is that the gtkdoc
The install directories of those targets that match the default
install directories have been removed because they are redundant.
This also allows a simple meson build files and it is unnecessary
to create some paths.
---
clients/cli/meson.build | 3 +--
clients/meson.build | 3 +--
The unused-but-set warning has recently been enabled in autotools
(e912b36d95a3c26a6021eeb27e663bd05910a9b4), so this also modifies
meson to enable it.
---
meson.build | 1 -
1 file changed, 1 deletion(-)
diff --git a/meson.build b/meson.build
index 6d0b29592..11e6cdd90 100644
--- a/meson.build
+
Documentation was not working in meson due to problems with files
generated in `libnm`. To avoid these problems, workarounds were
used. This problems have been recently fixed so these workarounds
are not necessary anymore.
---
clients/common/meson.build | 4 +---
docs/api/meson.build | 4 +--
Since meson 0.44 there is a new option type called `array`, which
allows to use an array with different values in those options.
These fits the needs of different options that are used to pass
binary paths, which have multiple paths as an alternate locations.
meson's version has been bumped to 0.
Both meson and autotools define HAVE_VLAN_FLAG_LOOSE_BINDING to 1 or
0 depending if a small code snippet is compiled. However, this define
is not used anymore.
---
config.h.meson | 3 ---
configure.ac | 22 --
meson.build| 15 ---
3 files changed, 40 deletion
Source files for enum types are generated by passing segments of the
source code of the files to the `glib-mkenums` command.
This patch removes those parameters where source code is used from
meson build files by moving those segmeents to template files.
---
clients/cli/meson.build
There are three headers `nm-secret-agent-old.h`,
`nm-vpn-plugin-old.h`, and `nm-vpn-service-plugin.h`, which are
named as no introspection headers. However, these files also
join to the rest headers to generate introspection data.
This patch merges those no introspection headers with the public
he
`generate-plugin-docs.pl` script which is used to parse
`nm-setting-c*.c` files depends on autotools. This is because it
parses the `Makefile.am` in order to figure out the setting files
it needs to parse.
This patch makes the script independent of autotools by passing
the necessary setting files
The `libnm_linking` test that belongs to the libnm-util's general
tests is failing because the test is not able to find the
`test-libnm-linking` binary, which is executed as a child process.
The problem lies to the `BUILD_DIR` macro definition which is
used to set the place to find the binary, and
There are some tests located in different directories which are
using the same name. To avoid any confussion a prefix was used to
name the test and the target.
This patch uses the prefix just for the target, to avoid any
collision that may happen, and uses the `test-` pattern as the
name.
---
cli
The `test-ndisc-linux` test is being run as an unit test. However,
it is not meant to be run as one of them.
This patch simply builts it as not installable binary.
---
src/ndisc/tests/meson.build | 34 +++---
1 file changed, 19 insertions(+), 15 deletions(-)
diff --gi
Thanks! I was thinking on using the `add_argument`'s `default`
parameter, but I must have forgotten it.
Best regards,
2017-12-14 15:26 GMT+01:00 Thomas Haller :
> On Thu, 2017-12-14 at 12:58 +0100, Iñigo Martínez wrote:
>> The following two patches fix the problem with the gen
This patch uses the recently added `--lib-path` parameter to pass the
`libnm`'s built directory, which allows the proper generation of the
files in meson.
For correctness, the `libnm` target has also been added as dependency
for both targets, even though there is an indirect dependency through
`li
The following two patches fix the problem with the generation of the
`nm-settings-docs.xml` and `nm-property-docs.xml` files, which made
the meson build port to fail when documentation generation was
enabled.
This patch adds a new optional parameter, `-l` or `--lib-path` that
can be used to pass d
2017-11-08 18:56 GMT+01:00 Colin Helliwell :
>
>> On 08 November 2017 at 16:54 Thomas Haller wrote:
>>
>> On Wed, 2017-11-08 at 13:40 +0100, Iñigo Martínez wrote:
>>
>> > Hi all,
>> >
>> > These past few months I have been porting some l
2017-11-08 17:54 GMT+01:00 Thomas Haller :
> On Wed, 2017-11-08 at 13:40 +0100, Iñigo Martínez wrote:
>> Hi all,
>>
>> These past few months I have been porting some libraries and
>> applications to meson build system[0], within the "MesonPorting"
>> init
Hi all,
These past few months I have been porting some libraries and
applications to meson build system[0], within the "MesonPorting"
initiative[1] that tries to port packages under GNOME umbrella to
meson.
As you may know, meson is a new build system which offers some
benefits over autotools, of
31 matches
Mail list logo
