summaryrefslogtreecommitdiff
path: root/.github
AgeCommit message (Collapse)AuthorFilesLines
2023-09-18CI: Use git master for xkeyboard-config on LinuxPierre Le Marre1-0/+13
xkeyboard-config and xkbcommon projects are quite intertwined so we want things to blow up early. It also solves an issue with the x11comp test.
2023-07-04Check the doxygen versionPeter Hutterer1-0/+8
Doxygen 1.9.7 breaks our urls, see issue #347. Let's put a check for the doxygen version into our CI build so that if our base distro updates beyond that, the CI fails and we know we have to build doxygen from scratch or update to some other version that's supported. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2023-07-04Configure github pagesPeter Hutterer2-1/+63
Upload the doxygen output as artifact from the linux build and use that from the pages job where we combine the static website with our newly build HTML docs. The GitHub actions/download-artefact doesn't work across workflows so we use the other popular one that can do this. The rest of the job is basically copy/paste from the "Static HTML" example GitHub provides. To make this useful as drop-in replacement, replace the one fixed link to the API docs a relative one. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2023-06-26CI: Fix documentation generation for macOSPierre Le Marre1-1/+5
- Force Doxygen version 1.9.6, because 1.9.7 breaks our doc cool URIs, i.e. our system that maintain stable doc pages via redirection. Associated issue in Doxygen: https://github.com/doxygen/doxygen/issues/10146 - Install graphviz to build the .dot files.
2023-05-14Add support for stable doc URLs (#342)Wismill2-2/+2
Doc URLs may change with time because they depend on Doxygen machinery. This is unfortunate because it is good practice to keep valid URLs (see: https://www.w3.org/Provider/Style/URI.html). I could not find a built-in solution in Doxygen, so the solution proposed here is to maintain a registry of all URLs and manage legacy URLs as redirections to their canonical page. This commit adds a registry of URLs that has three functions: - Check no previous URL is now invalid. - Add aliases for moved pages. - Generate redirection pages for aliases. The redirection works with a simple <meta http-equiv="refresh"> HTML tag. See: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta#http-equiv This commit also initialize the URLs registry with current pages and some redirections needed after recent documentation refactoring. Finally, the CI is updated to catch any change that invalidate previous URLs.
2023-05-12ci: bump runs-on versionsRan Benita4-7/+8
Mostly to bump to macos one which will hopefully fix CI issues there. Signed-off-by: Ran Benita <ran@unusedvar.com>
2023-05-05ci/windows: use the vs backend instead of ninja backendRan Benita1-5/+1
So we have some coverage of that. Signed-off-by: Ran Benita <ran@unusedvar.com>
2022-12-16ci: don't run linux on push to non-master branchesRan Benita1-1/+5
It's redundant with the pull request run. Signed-off-by: Ran Benita <ran@unusedvar.com>
2022-12-14CI: bump a few actions to newer versionsPeter Hutterer4-7/+7
Node 12 is deprecated so let's bump the actions to newer versions that use Node 16. See https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/
2022-09-24ci/linux: store the test logs as artifacts on failurePeter Hutterer1-0/+7
This makes debugging a lot easier than having to reproduce locally. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2022-09-24ci/linux: split normal testing from valgrind testingPeter Hutterer1-0/+3
A test case failure usually also triggers valgrind leaks, sifting through those to find the actual test failure is painful. So let's separate the tests and run them separately. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2022-03-20ci/linux: bring back `apt update` to fix `apt install` 404sRan Benita1-0/+1
Signed-off-by: Ran Benita <ran@unusedvar.com>
2022-02-04ci: another possible fix for release workflowRan Benita1-1/+1
Signed-off-by: Ran Benita <ran@unusedvar.com>
2022-01-17CI: always run the linux workflowPeter Hutterer1-5/+1
This makes it easier for contributors to check if their code runs correctly without having to file a PR. The Mac and Windows workflows are a bit more involved, so let's keep those on pull requests only.
2022-01-17CI: split and rename the workflows to windows/macos/linuxPeter Hutterer4-108/+130
"main" is a bit non-descriptive, let's name them after the platforms we run them on. Splitting them up allows us to be less selective on how we run the various workflows, e.g. always running the linux one.
2021-09-17ci: possible fix for release workflowRan Benita1-1/+1
Signed-off-by: Ran Benita <ran@unusedvar.com>
2021-05-22ci: some tweaksRan Benita2-12/+35
- Reduce permissions - Update some stuff Signed-off-by: Ran Benita <ran@unusedvar.com>
2021-05-22ci: also link to tarball in github releaseRan Benita1-1/+3
Signed-off-by: Ran Benita <ran@unusedvar.com>
2021-05-22ci: automatically create github release when tag is pushedRan Benita1-0/+21
Fixes: https://github.com/xkbcommon/libxkbcommon/issues/233 Signed-off-by: Ran Benita <ran@unusedvar.com>
2020-11-19ci: fix windows CI failure due to add-path deprecationRan Benita1-1/+1
Signed-off-by: Ran Benita <ran@unusedvar.com>
2020-09-07ci: enable xkbregistry on macos jobRan Benita1-2/+2
Signed-off-by: Ran Benita <ran@unusedvar.com>
2020-08-31ci: fix windows job not finding bisonRan Benita1-8/+6
Instead of using the unpredictable chocolatey let's just handle it ourselves. The versions are pinned but that's arguably good. Fixes https://github.com/xkbcommon/libxkbcommon/issues/179 Signed-off-by: Ran Benita <ran@unusedvar.com>
2020-07-25Drop use of ronn, switch to raw roff insteadPeter Hutterer1-5/+1
Drop the ronn source files, check in the generated files instead. This gets rid of the ruby+gem+ronn toolchain requirement at the cost of having to edit raw man pages. ronn files are as-generated but with the preamble and generation date removed. The latter isn't important enough to keep, it'll just go stale for manually maintained files and it's not worth setting up a configure_file() just for that date. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2020-07-25tools: add a xkbcli tool as entry point for the various tools we havePeter Hutterer1-1/+5
This is the base tool, no subtools are currently connected so you only get help and version for now. The goal here is to have a git-like infrastructure where /usr/bin/xkbcli is the main tool, anything else will hide in libexec. The infrastructure for this is copied from libinput. Tools themselves will will be installed in $prefix/libexec/xkbcommon and the xkbcli tool forks off whatever argv[1] is after modifying the PATH to include the libexec dir. libinput has additional code for checking whether we're running this from the builddir but it's a bit iffy and it's usefulness is limited - if you're in the builddir anyway you can just run ./builddir/xkbcli-<toolname> directly. So for this code here, running ./builddir/xkbcli <toolname> will execute the one in the prefix/libexecdir. Since we want that tool available everywhere even where some of the subtools aren't present, we need to ifdef the getopt handling. man page generation is handled via ronn which is a ruby program but allows markdown for the sources. It's hidden behind a meson option to disable where downloading ronn isn't an option. The setup is generic enough that we can add other man-pages by just appending to the array. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2020-07-25meson.build: add the valgrind test setup, exclude python testsPeter Hutterer1-1/+1
This way we can invoke the expected setup with meson test --setup=valgrind And because we don't care about valgrinding python script, mark that test as part of the "python-tests" suite and skip it during our CI valgrind run. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Ran Benita <ran@unusedvar.com>
2020-07-25test: make the symbols-leak-test executablePeter Hutterer1-1/+1
Python leaks like crazy when run under valgrind. But if we make the script executable **and** it has uses the env invocation (i.e. #!/usr/bin/env python3), the leaks disappear. This is not the case for a shebang of /usr/bin/python3. Why exactly this is the case I'm not sure but executables we plan to run should have the exec bit set. So this is a janitor patch with the nice side effect of fixing our valgrind runs. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2020-07-22test: fix Windows CI by rewriting symbols-leak-test from bash to pythonRan Benita1-1/+1
The CI started installing some wrapper instead of a real bash which is what gets found. See: https://github.com/actions/virtual-environments/pull/1081 Given meson is written in python, it should always be available hopefully. Disabled valgrind wrapper for now because it now also applies to the python interpreter which leaks like a sieve. Signed-off-by: Ran Benita <ran@unusedvar.com>
2020-07-22ci: cache chocolaty downloadRan Benita1-0/+7
The bison sourceforge download is quite slow and unreliable. Hopefully this works. Stolen directly from ruby: https://github.com/ruby/ruby/blob/a50750c8a960ef62b3e1dbd78b12056f0512b17d/.github/workflows/windows.yml#L26 Signed-off-by: Ran Benita <ran@unusedvar.com>
2020-07-06Add libxkbregistry to query available RMLVOPeter Hutterer1-2/+2
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>
2020-04-18ci: add github actions buildRan Benita1-0/+89
We currently use Azure Pipelines. But it became out of date. Also it requires a different account and setup than github account itself. The configuration here is probably not very good and is less featureful than the Azure one but it's what I managed. Signed-off-by: Ran Benita <ran@unusedvar.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-24 20:55:26 +0000