| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
And the files to be skipped.
|
|
|
|
| |
We renamed it to gweather4 from gweather-4.0.
|
|
|
|
|
| |
Use a format more suited to gi-docgen's output, and try to make it more
human readable.
|
|
|
|
| |
There's no point in using the full "N.0" version.
|
|
|
|
|
| |
There's no point in having it at the bottom of the meson.build file in
the top-level directory.
|
| |
|
|
|
|
| |
Otherwise we're going to overwrite libgweather-3 files.
|
|
|
|
| |
Drop gtk3-devel and add gdk-pixbuf2-devel.
|
|
|
|
|
|
|
|
|
| |
The GTK3 widgets cannot exist in the same process as other versions of
GTK, which means applications cannot port to GTK4 and link to
libgweather.
If we want to add GTK widgets back to libgweather we are going to do so
in a separate shared library, with a separate namespace.
|
|
|
|
| |
Update the links and various other details.
|
|
|
|
|
| |
We know the ABI is going to change, but we're also going to keep the API
stable after the next major release.
|
|
|
|
|
| |
We are going to guarantee the API stability of this library going
forward.
|
|
|
|
|
|
| |
The major API has been reset, there's no need to have a "Since"
annotation, as all symbols are available from this version until the
next major API break.
|
|
|
|
|
|
|
|
|
|
|
|
| |
We're now at 4.0. The version bump requires some additional changes:
- the project version is 3.90, while we are in a development cycle
- the main gettext domain has been changed to libgweather-4.0
- the gettext domain for the locations has been changed to
libgweather-4.0-locations
- the settings schemas have been changed to org.gnome.GWeather4
- the soname of the shared library has been changed to match the
versioning scheme used by GLib and GTK
|
|
|
|
|
|
|
|
|
| |
Libgweather is a C library, and it's reading and parsing files, and
poking at web services: we should really be doing some minimum safety
checks that our code isn't just an exploit waiting to happen.
For the time being, both jobs are marked to allow failure, with the
explicit intent to lead us towards fixing the issues they find.
|
|
|
|
|
|
|
| |
- Transfer the GMappedFile to the world database only on success
- Move declarations inside the load block
- Add explicit pointer comparisons
- Match the definition with the declaration, by adding `void`
|
|
|
|
| |
Instead of writing the get_type() function ourselves.
|
|
|
|
| |
Instead of writing the get_type() function ourselves.
|
|
|
|
| |
We're using gi-docgen, and we rely on types.
|
|
|
|
| |
This way it's going to be slightly easier to check for issues.
|
|
|
|
| |
Tell GitLab to use the JUnit report provided by Meson.
|
|
|
|
|
|
|
| |
- Add base recipes to be reused for different jobs
- Split the ABI check into its own stage
- Build the API reference in its own stage
- Publish the API reference with GitLab Pages
|
|
|
|
|
| |
Now that it's fast and does not have a lot of extra dependencies, we can
build the libgweather API reference by default.
|
|
|
|
|
|
|
|
|
| |
When building libgweather as a subproject or as a Flatpak module we may
want to disable generating the introspection data if we know we're only
ever going to consume the C API.
Disabling introspection will disable the documentation and the VAPI file
generation as a side effect.
|
|
|
|
|
|
| |
Gtk-doc is currently unmaintained, and fairly slow.
Gi-docgen uses the introspection data to generate the documentation.
|
|
|
|
|
| |
Don't bunch up everything together: we can spare a newline between
enumeration types.
|
|
|
|
| |
Instead of hand-coding it ourselves.
|
|
|
|
| |
As well as a way to disable them.
|
|
|
|
| |
They are very non-descriptive as "read me" files.
|
|
|
|
| |
The authors of libgweather are included in the Git commit log.
|
|
|
|
|
| |
And make sure to use the path of the script returned by
`find_program()`, instead of using `files()`.
|
| |
|
|
|
|
|
|
| |
We should write tests and tools that look like tests in the same way
we'd write code that depends on the library, instead of assuming that
everything works out because it sits in the same directory.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All symbols should be hidden by default, and public symbols should be
explicitly annotated.
Once we commit to a stable API/ABI, we will be able to use versioned
macros to mark symbols for deprecation, and get compiler warnings that
can be toggled on and off by consumers of our API.
The current symbol visibility map includes two private symbols used by
our tests; to avoid this leakage, we can build libgweather as a static
library, and then use the static library for our tests and as the base
of our public shared library.
|
|
|
|
|
| |
This way, GitLab will pick up the file and link to it in the project
page.
|
|
|
|
|
|
| |
Remove dead/outdated links, and make it more newcomer friendly, by
clearly stating the expectations on both the contributor and maintainer
side.
|
|
|
|
| |
It's advisory, and currently unused, but it's handy to have.
|
|
|
|
|
|
| |
We're not using Autotools, and people should not copy-paste random files
from libgweather without the configuration header. That's why we have a
library.
|
|
|
|
| |
All source files include should "config.h" themselves.
|
|
|
|
|
|
| |
- Use SPDX tags for copyright and license
- Include "config.h" unconditionally, we're not using Autotools
- Include the local headers first
|
|
|
|
|
|
|
|
| |
- Drop the GLib C alias types, and use the proper types
- Use consistent whitespace
- Do not align the functions; private headers are touched more often
than public ones, and realigning the whole header every time is just a
waste of time
|
|
|
|
|
|
| |
- Use a consistent coding style
- Use #pragma once for the inclusion guard
- Use SPDX license and copyright fields
|
|
|
|
| |
And drop the "not fully maintained" comment.
|
|
|
|
|
| |
We only use unsigned integers for indices, which means the "greater than
zero" check is redundant—and the compiler will tell us that.
|
|
|
|
|
| |
Change the template to use g_once_init_enter/leave pairs, like everyone
else does.
|
|
|
|
|
| |
We want the default warnings from Meson for warning_level=2, but we also
want to inject our own compiler arguments.
|
|
|
|
| |
It's 2021, there's no point in sticking with a C89 baseline.
|
| |
|
|
|
|
| |
Enable warnings, and produce debug-optimized builds by default.
|