nixpkgs/pkgs/by-name/wl/wlcs/package.nix
aleksana 571c71e6f7 treewide: migrate packages to pkgs/by-name, take 1
We are migrating packages that meet below requirements:

1. using `callPackage`
2. called path is a directory
3. overriding set is empty (`{ }`)
4. not containing path expressions other than relative path (to
makenixpkgs-vet happy)
5. not referenced by nix files outside of the directory, other
than`pkgs/top-level/all-packages.nix`
6. not referencing nix files outside of the directory
7. not referencing `default.nix` (since it's changed to `package.nix`)
8. `outPath` doesn't change after migration

The tool is here: https://github.com/Aleksanaa/by-name-migrate.
2024-11-09 20:04:51 +08:00

74 lines
1.9 KiB
Nix

{ stdenv
, lib
, gitUpdater
, fetchFromGitHub
, testers
, cmake
, pkg-config
, boost
, gtest
, wayland
, wayland-scanner
}:
stdenv.mkDerivation (finalAttrs: {
pname = "wlcs";
version = "1.7.0";
src = fetchFromGitHub {
owner = "MirServer";
repo = "wlcs";
rev = "v${finalAttrs.version}";
hash = "sha256-BQPRymkbGu4YvTYXTaTMuyP5fHpqMWI4xPwjDRHZNEQ=";
};
strictDeps = true;
nativeBuildInputs = [
cmake
pkg-config
wayland-scanner
];
buildInputs = [
boost
gtest
wayland
wayland-scanner # needed by cmake
];
passthru = {
tests.pkg-config = testers.testMetaPkgConfig finalAttrs.finalPackage;
updateScript = gitUpdater {
rev-prefix = "v";
};
};
meta = with lib; {
description = "Wayland Conformance Test Suite";
longDescription = ''
wlcs aspires to be a protocol-conformance-verifying test suite usable by Wayland
compositor implementors.
It is growing out of porting the existing Weston test suite to be run in Mir's
test suite, but it is designed to be usable by any compositor.
wlcs relies on compositors providing an integration module, providing wlcs with
API hooks to start a compositor, connect a client, move a window, and so on.
This makes both writing and debugging tests easier - the tests are (generally)
in the same address space as the compositor, so there is a consistent global
clock available, it's easier to poke around in compositor internals, and
standard debugging tools can follow control flow from the test client to the
compositor and back again.
'';
homepage = "https://github.com/MirServer/wlcs";
changelog = "https://github.com/MirServer/wlcs/releases/tag/v${finalAttrs.version}";
license = licenses.gpl3Only;
maintainers = with maintainers; [ OPNA2608 ];
platforms = platforms.linux;
pkgConfigModules = [
"wlcs"
];
};
})