Building libqrtr-glib 1.2 or later with Meson
The first stable series with support for building with the meson suite is 1.2. All the older stable series before 1.2 exclusively used the GNU autotools build system.
Building from a git checkout
When using meson, the builds are always triggered from git checkouts, there is no source release tarball involved. The basic build steps would be as follows:
$ git clone --depth 1 https://gitlab.freedesktop.org/mobile-broadband/libqrtr-glib.git $ cd libqrtr-glib $ meson setup build --prefix=/usr $ ninja -C build
Additional optional switches that may be given to the
meson command above would be:
- In Debian/Ubuntu systems the default location for libraries depends on the architecture of the build, so instead of the default
/usr/libpath that would be in effect due to
--prefix=/usr, the user should also give an explicit
--libdirpath pointing to the correct location. E.g. on a 64bit Ubuntu/Debian build, the user would use
- The gtk-doc documentation is disabled by default. In order to enable it, the additional
-Dgtk_doc=trueswitch should be given.
- The GObject introspection support is enabled by default. In order to disable it, the additional
-Dintrospection=falseswitch should be given.
- The default build type in meson if none explicitly specified is
debug, which means debug symbols are included and optimization is fully disabled. The
--buildtype=releaseswitch can be used to remove debug symbols and to enable optimization level to the maximum.
An example project build using all the above optional switches could be:
$ meson setup build \ --prefix=/usr \ --libdir=/usr/lib/x86_64-linux-gnu \ --buildtype=release \ -Dgtk_doc=true \ -Dintrospection=false $ ninja -C build
The installation on the prefix selected during
meson setup can be done with the following command:
$ sudo ninja -C build install
Please note that the command above will install the library in the system default path for libraries, possibly overwriting any previous libqrtr-glib library that may already exist from a package manager installed package. See the FAQ section for comments on how to install in
If you have manually installed the project with the steps above, it can be uninstalled in the same way:
$ sudo ninja -C build uninstall
If the manual install overwrote the package manager installed files, it is suggested to force a re-install of the corresponding packages at this point, so that the system is not left with missing files.