653ff6ba9e
Mutter wants sysprof's exact dbus interface directory during build time
* https://gitlab.gnome.org/GNOME/mutter/blob/master/src/meson.build#L714
On certain platforms mutter's datadir != sysprof's datadir.
This is initial work for a forthcoming PR to do
```
sysprof_dep.get_pkgconfig_variable('datadir')
```
in mutter for compatibility with these platforms.
This patch is on behalf of nixpkgs where we actually have to carry a
downstream patch [0] for this exact reason. We install everything into
their own immutable prefix under `/nix/store`.
[0]: a821167046/pkgs/desktops/gnome-3/core/mutter/0001-build-use-get_pkgconfig_variable-for-sysprof-dbusdir.patch
Sysprof is a sampling profiler that uses a kernel module to generate stacktraces which are then interpreted by the userspace program "sysprof".
See the Sysprof homepage for more information.
Questions, patches and bug reports should be sent to the sysprof mailing list sysprof-list@gnome.org.
The list is archived in https://mail.gnome.org/archives/sysprof-list/.
Debugging symbols
The programs and libraries you want to profile should be compiled
with -fno-omit-frame-pointer and have debugging symbols available,
or you won't get much usable information.
Building Sysprof
You need some packages installed. The package names may vary depending on your distribution, the following command works on Fedora 25:
sudo dnf install gcc gcc-c++ ninja-build gtk3-devel
Then do the following:
meson --prefix=/usr build
cd build
ninja
sudo ninja install
WARNING: ninja install will mostly install under the configured install
prefix but installs systemd service configuration directly in the system
default location /usr/lib/systemd so it won't work without root privileges,
even if the install prefix is a user-owned directory.