summaryrefslogtreecommitdiff
path: root/PACKAGING
Commit message (Collapse)AuthorAgeFilesLines
* PACKAGING: mention xkbcliRan Benita2020-08-301-0/+3
| | | | Signed-off-by: Ran Benita <ran@unusedvar.com>
* PACKAING: remove bashRan Benita2020-07-221-1/+1
| | | | | | Converted to Python. Signed-off-by: Ran Benita <ran@unusedvar.com>
* Add libxkbregistry to query available RMLVOPeter Hutterer2020-07-061-3/+25
| | | | | | | | | | | | | | | | | | | | | This library is the replacement for clients parsing evdev.xml directly. Instead, they should use the API here so that in the future we may even be able to swap evdev.xml for a more suitable data format. The library parses through evdev.xml (using libxml2) and - if requested - through evdev.extras.xml as well. The merge approach is optimised for the default case where we have a system-installed rules XML and another file in $XDG_CONFIG_DIR that adds a few entries. We load the system file first, then append any custom ones to that. It's not possible to overwrite the MLVO list provided by the system files - if you want to do that, get the change upstream. XML validation is handled through the DTD itself which means we only need to check for a nonempty name, everything else the DTD validation should complain about. The logging system is effectively identical to xkbcommon. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* meson.build: Take win_bison as a possible variant for BisonAdrian Perez de Castro2019-12-271-1/+1
| | | | Signed-off-by: Ran Benita <ran@unusedvar.com>
* README,PACKAGING: use the new meson unified command formatRan Benita2017-12-151-1/+1
| | | | Signed-off-by: Ran Benita <ran234@gmail.com>
* build: add meson build systemRan Benita2017-07-311-12/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Meson is easier to maintain, much faster, encourages better practices, and is not built on a pile of shell scripts. The autotools build system is kept intact for now, in order to ease the migration. The intention is to remove it sooner rather than later, if all goes well. Run `meson build && mesonconf build` to see the configuration options for the new system. Conversion should be straightforward. Environment variables like CFLAGS work the same. If meson is used, xorg-util-macros is not required. In terms of functionality the two systems have about the same capabilities. Here are some differences I noticed: - Meson uses `-g` by default, autotools uses `-g -O2`. - In autotools the default behavior is to install both static and shared versions of the libraries. In meson the user must choose exactly one (using -Ddefault_library=static/shared). It is possible to workaround if needed (install twice...), but hopefully meson will add the option in the future. - Autotools has builtin ctags/cscope targets, meson doesn't. Easy to run the tools directly. - Meson has builtin benchmarks target. Handy. - Meson has builtin support for sanitizers/clang-analyzer/lto/pgo/ coverage etc. Also handy. Signed-off-by: Ran Benita <ran234@gmail.com>
* build: move custom targets to scripts/ and remove from makefileRan Benita2017-07-311-1/+1
| | | | | | | These scripts generate source code that is committed to git and hence do not really belong in the build system. A maintainer runs them as needed. Signed-off-by: Ran Benita <ran234@gmail.com>
* PACKAGING: Update for interactive-waylandDaniel Stone2016-06-211-0/+5
| | | | Signed-off-by: Daniel Stone <daniels@collabora.com>
* PACKAGING: fix confusing typoRan Benita2014-10-241-1/+1
| | | | Signed-off-by: Ran Benita <ran234@gmail.com>
* Add PACKAGING fileRan Benita2014-10-181-0/+50
Signed-off-by: Ran Benita <ran234@gmail.com>