| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
NOTICE: Future-deprecated features used:
* 0.55.0: {'ExternalProgram.path'}
* 0.56.0: {'meson.source_root', 'meson.build_root'}
|
|
|
|
|
|
|
|
|
|
|
|
| |
Connect and monitor UPower devices for devices reporting their battery
status.
This makes sure that we can show battery status for devices
that emit their battery status through bluez (via the BATT LE service,
or the org.bluez.BatteryProviderManager1 API, as well as devices for
which the kernel is the battery info provider.
Closes: #102
|
| |
|
| |
|
|
|
|
|
| |
Now that libadwaita has the header-suffix property,
we can use AdwPreferencesGroup's built-in header.
|
|
|
|
| |
We'll need it before meson configures itself soon.
|
| |
|
|
|
|
|
|
| |
Both UI and non-UI libraries export a pkg-config file. Only the non-UI
library exports a Gir as it's the only one that gets to be used from a
non-native program (gnome-shell).
|
| |
|
|
|
|
|
|
|
|
|
| |
Currently, both gnome-bluetooth-1.0 and 2.0 are using "2"
as a suffix for the gettext locale files which causes them to
overalp. Looks like 2 has been used since the initial commit
of the meson port, back in 3.20 cycle, although not sure if
there is any special meaning to the number. Bump it anyway
so that translations won't overlap between the two versions.
|
|
|
|
| |
To match the software's version number too.
|
| |
|
|
|
|
|
| |
It won't be used by anything in GNOME, as we prefer symbolic icons, and
Adwaita provide some already.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Remove the in-tree widget, and replace the type ensure with
ADW_TYPE_CLAMP.
|
|
|
|
| |
Switch the build system to GTK4. This breaks the build quite intensely.
|
|
|
|
|
|
|
|
|
|
|
|
| |
We're about to break the public API due to the GTK4 transition
so preemptively bump the API version. However, given that GNOME
Shell uses gnome-bluetooth (and has other GTK3 dependencies),
making gnome-bluetooth-2.0 parallel installable is our only option.
Bump the API version, and make gnome-bluetooth-2.0 parallel
installable with 1.0. Do that by using the 'gnomebt_api_name'
meson variable, which contains meson.project_name() + API version,
as the library name and install location.
|
|
|
|
|
|
|
|
|
|
|
| |
Mainly to reduce the number of GTK3 dependencies before actually start
porting the library. Fortunately, the usage of libcanberra-gtk by
gnome-bluetooth is rather trivial, so porting to gsound is just a few
lines of code away.
Replace canberra-gtk by gsound, adjust the build system to reflect
that, and update the CI file to install gsound-devel instead of
libcanberra-devel.
|
| |
|
|
|
|
|
|
|
|
| |
The documentation we brought forward from autotools/libtool didn't
actually match sonames, but used libtool rules. Replicate the libtool
rules to fix the unwanted soname bump.
Closes: #82
|
| |
|
|
|
|
|
|
|
|
|
|
| |
A build with -Dintrospection=false will fail if tests are ran.
The integration tests added by commit 77b67c702 are written in
Python and require gobject-introspection bindings to be generated.
meson errors out with:
../tests/meson.build:7:0: ERROR: Unknown variable "gnomebt_priv_gir".
|
| |
|
|
|
|
| |
Add a simple test using python-dbusmock to test out some of our code.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The 3.29 release cycle has already come and gone, we should be releasing
for the 3.31 cycle.
|
| |
|
|
|
|
| |
Fixes https://gitlab.gnome.org/GNOME/gnome-control-center/issues/364
|
|
|
|
|
|
| |
This will be needed by the next commit to access HdyColumn.
This also lets the CI recursively update the submodules so it can pass.
|
|
|
|
|
|
|
|
|
|
|
|
| |
libgnome-bluetooth expose a number of includes in their public
headers belonging to different libraries. Therefore, these libraries
are indirect dependencies of the library to be built.
With this in mind, required dependencies have been split in two
sets, one formed by public dependencies and the other by private
dependencies.
The created `pkg-config` file now also use these new sets.
|
|
|
|
|
|
|
|
|
| |
Although usually directory variables are set by using the `prefix`
directory, this might cause issues due to parameters that need
relative directories.
In order to ease the transition `prefix` directory has been stripped
from directory variables and only has been appended when necessary.
|
|
|
|
|
|
|
|
|
| |
Since meson 0.49, the `/` character can be used to join paths[0], so
all the instances of `join_paths` have been replaced.
Required meson version has been bumped to 0.49.
[0] http://mesonbuild.com/Release-notes-for-0-49-0.html#joining-paths-with-
|