summaryrefslogtreecommitdiff
path: root/meson.build
Commit message (Collapse)AuthorAgeFilesLines
* Fixed version number to 2.38xkeyboard-config-2.38Sergey Udaltsov2023-02-041-1/+1
|
* Preparing 2.38Sergey Udaltsov2023-02-041-1/+1
|
* prerelease push, for translationsSergey Udaltsov2023-01-221-1/+1
|
* Release 2.37xkeyboard-config-2.37Sergey Udaltsov2022-10-041-1/+1
|
* Prepare 2.37Sergey Udaltsov2022-09-151-1/+1
|
* man: drop the custom man suffixesPeter Hutterer2022-07-061-2/+0
| | | | | | Everyone's using the same numbers now. Welcome to the future. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* Release 2.36xkeyboard-config-2.36Sergey Udaltsov2022-06-011-1/+1
|
* PrereleaseSergey Udaltsov2022-05-241-1/+1
| | | | 2.35.99
* Release 2.35xkeyboard-config-2.35Sergey Udaltsov2022-02-071-1/+1
|
* preparing for new translationsSergey Udaltsov2022-02-071-1/+1
|
* again 2.34xkeyboard-config-2.34Sergey Udaltsov2021-10-041-1/+1
|
* revert to prereleaseSergey Udaltsov2021-10-041-1/+1
|
* Release 2.34Sergey Udaltsov2021-10-041-1/+1
|
* PrereleaseSergey Udaltsov2021-10-041-1/+1
|
* Release 2.33xkeyboard-config-2.33Sergey Udaltsov2021-06-081-1/+1
|
* Move the evdev.in and inet.in template file to the gitlab-ci directoryPeter Hutterer2021-04-121-1/+1
| | | | | | | | These don't need to sit in the main source tree where we need exceptions for them in the build system. They are only called from special jobs in the CI pipelines, so let's move this to the CI directory. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* meson.build: don't install inet.inPeter Hutterer2021-04-061-1/+1
| | | | | | Follow-up from !172, introduced in 2a0c538 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* gitlab CI: generate the evdev keycodes (v2)Peter Hutterer2021-02-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | The various <I123> keycodes in keycodes/evdev simply match the kernel defines + offset 8. There is no need to maintain these manually, let's generate them instead. Keycodes update rarely and irregularly (on average maybe every second kernel release) so there's no need to integrate this into the build itself, let's add it to our CI instead. The script here uses python-libevdev which has a list of the various key codes and their names (compile-time built-in in libevdev itself so it's advisable that a recent libevdev is used). The script is hooked up to a custom job that will fail if there are key codes with a #define in the kernel that are not listed in our evdev file. We allow that job to fail, it's not that urgent to block any merge requests. Changes to v1, see commit 5dc9b48c and its revert 8fa3b314: - Parse the template for existing defines and alias those keys. e.g. alias <I121> = <MUTE>; - Kernel v5.10 keycodes are now included in the file - The script defaults to the correct template/keycode file, no commandline arguments needed for the default run. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* Release 2.32xkeyboard-config-2.32Sergey Udaltsov2021-02-161-1/+1
|
* Revert "gitlab CI: generate the evdev keycodes"Peter Hutterer2021-01-211-1/+1
| | | | | | | | | | | | | | | Some of the generated keys overwrote existing keys, causing warnings and nonfunctional keys. For example: xkbcommon: WARNING: Multiple names for keycode 121; Using <I121>, ignoring <MUTE> Revert this commit, we're too close to a release and it's better to wait until the next one to give this approach more time to settle. Fixes #247 This reverts commit 5dc9b48c9b31de9f9780887a79ded3b1e52591d9. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* PrereleaseSergey Udaltsov2021-01-201-1/+1
|
* gitlab CI: generate the evdev keycodesPeter Hutterer2021-01-181-1/+1
| | | | | | | | | | | | | | | | | | | The various <I123> keycodes in keycodes/evdev simply match the kernel defines + offset 8. There is no need to maintain these manually, let's generate them instead. Keycodes update rarely and irregularly (on average maybe every second kernel release) so there's no need to integrate this into the build itself, let's add it to our CI instead. The script here uses python-libevdev which has a list of the various key codes and their names (compile-time built-in in libevdev itself so it's advisable that a recent libevdev is used). The script is hooked up to a custom job that will fail if there are key codes with a #define in the kernel that are not listed in our evdev file. We allow that job to fail, it's not that urgent to prevent any other pipelines. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* Preparing releaseSergey Udaltsov2020-10-071-1/+1
|
* preparing new releaseSergey Udaltsov2020-09-251-1/+1
|
* meson.build: this is not a 'c' language projectPeter Hutterer2020-09-031-1/+1
| | | | | | | | | | We don't need a compiler, let's drop this from meson.build. Unfortunately, the AM_GNU_GETTEXT macro introduces a compiler dependency, so we can't get rid of it in the list of required packages for CI, at least not while we're building with autotools. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* Add support for the meson build systemPeter Hutterer2020-06-191-0/+63
This produces virtually the same installed tree as the autotools builds with the following exceptions: - rules symlinks is no longer supported. This option is 16y old and likely hasn't been used in the last decade or so - the xkeyboard-config.pc file uses expanded paths now, e.g. xkb_base=/usr/share/X11/xkb vs autotools' xkb_base=${datarootdir}/X11/xkb The values are the same for both so this is not a functional change. - substitutions in the man page are hardcoded since we can't use the m4 XORG_MACROS. This appears to only matter for the miscmansuffix and there only for solaris up to including 11.3. so... meh? - the .mo files differ, but it's hard to say why since they're generated Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
View Lorry Controller Status