StreetLight
/
libxkbcommon
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
libxkbcommon/PACKAGING

52 lines
1.8 KiB
Plaintext
Raw Normal View History

Add PACKAGING file Signed-off-by: Ran Benita <ran234@gmail.com>
2014-10-18 06:51:41 -06:00
libxkbcommon consists of two shared libraries, libxkbcommon (the main
library) and libxkbcommon-x11 (an addon library for XCB clients).
The files for libxkbcommon-x11 are:
PACKAGING: fix confusing typo Signed-off-by: Ran Benita <ran234@gmail.com>
2014-10-24 14:06:07 -06:00
libxkbcommon-x11.a libxkbcommon-x11.so* xkbcommon/xkbcommon-x11.h
Add PACKAGING file Signed-off-by: Ran Benita <ran234@gmail.com>
2014-10-18 06:51:41 -06:00
xkbcommon-x11.map xkbcommon-x11.pc
build: add meson build system 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>
2017-07-25 12:57:42 -06:00
libxkbcommon-x11 can be disabled with -Denable-x11=false (see
README,PACKAGING: use the new meson unified command format Signed-off-by: Ran Benita <ran234@gmail.com>
2017-12-15 07:17:45 -07:00
`meson configure build` for other options/variables).
Add PACKAGING file Signed-off-by: Ran Benita <ran234@gmail.com>
2014-10-18 06:51:41 -06:00
Dependencies for libxkbcommon:
build: add meson build system 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>
2017-07-25 12:57:42 -06:00
- C compiler, meson, pkg-config, libc, bash, grep, sed.
Add PACKAGING file Signed-off-by: Ran Benita <ran234@gmail.com>
2014-10-18 06:51:41 -06:00
meson.build: Take win_bison as a possible variant for Bison Signed-off-by: Ran Benita <ran@unusedvar.com>
2019-08-12 16:17:51 -06:00
- (build) bison (preferred), win_bison or byacc>=20141006.
Add PACKAGING file Signed-off-by: Ran Benita <ran234@gmail.com>
2014-10-18 06:51:41 -06:00
byacc must be configured with --enable-btyacc.
- (build optional, runtime) xkeyboard-config.
During build, for automatically detecting the value of
build: add meson build system 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>
2017-07-25 12:57:42 -06:00
-Dxkb-config-root instead of guessing (/usr/share/X11/xkb).
Add PACKAGING file Signed-off-by: Ran Benita <ran234@gmail.com>
2014-10-18 06:51:41 -06:00
During runtime, not strictly needed, but most users of the library
would need it.
- (runtime) libX11.
Contains the dataset for Compose support (/usr/share/X11/locale).
Please don't depend on it explicitly.
- (build optional) doxygen.
For generating the HTML documentation.
build: add meson build system 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>
2017-07-25 12:57:42 -06:00
To disable, use -Denable-docs=false.
Add PACKAGING file Signed-off-by: Ran Benita <ran234@gmail.com>
2014-10-18 06:51:41 -06:00
- (build optional) gperf.
Output included in git and tarball. To regenerate, use
build: move custom targets to scripts/ and remove from makefile 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>
2017-07-29 05:37:23 -06:00
`./scripts/update-keywords`.
Add PACKAGING file Signed-off-by: Ran Benita <ran234@gmail.com>
2014-10-18 06:51:41 -06:00
Dependencies for libxkbcommon-x11:
- libxkbcommon.
- libxcb>=1.10 with libxcb-xkb.
Dependencies for libxkbcommon-x11 tests:
- xkbcomp, Xvfb.
If they are not available, the relevant tests are skipped.
PACKAGING: Update for interactive-wayland Signed-off-by: Daniel Stone <daniels@collabora.com>
2016-04-12 06:47:26 -06:00
Dependencies for Wayland tests:
build: add meson build system 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>
2017-07-25 12:57:42 -06:00
- wayland-client>=1.2.0, wayland-scanner, wayland-protocols>=1.0.
To disable, use -Denable-wayland=false.
PACKAGING: Update for interactive-wayland Signed-off-by: Daniel Stone <daniels@collabora.com>
2016-04-12 06:47:26 -06:00
Add PACKAGING file Signed-off-by: Ran Benita <ran234@gmail.com>
2014-10-18 06:51:41 -06:00
Unless libxcb is always available as part of the system, it is preferred
that libxkbcommon and libxkbcommon-x11 be split into separate packages,
such that the main library does not depend on libxcb. This avoids a
transitive dependency of Wayland clients on X libraries.