Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to build or run the project #239

Open
saadahmsiddiqui opened this issue Sep 6, 2024 · 1 comment
Open

Unable to build or run the project #239

saadahmsiddiqui opened this issue Sep 6, 2024 · 1 comment

Comments

@saadahmsiddiqui
Copy link

saadahmsiddiqui commented Sep 6, 2024

Logs:

Compiling bitflags v2.6.0
   Compiling toml_datetime v0.6.8
   Compiling enumflags2 v0.7.10
   Compiling regex v1.10.6
   Compiling async-io v1.13.0
   Compiling smithay-client-toolkit v0.19.2
   Compiling lock_api v0.4.12
   Compiling tiny-skia v0.11.4
   Compiling owned_ttf_parser v0.24.0
   Compiling phf_shared v0.11.2
   Compiling smol_str v0.2.2
   Compiling crossbeam-epoch v0.9.18
   Compiling percent-encoding v2.3.1
   Compiling ab_glyph_rasterizer v0.1.8
   Compiling zerofrom v0.1.4
error: failed to run custom build command for `smithay-client-toolkit v0.19.2`

Caused by:
  process didn't exit successfully: `/home/saadjhk/Desktop/cosmic-edit/target/debug/build/smithay-client-toolkit-e5d0280e5ab9b95b/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-env-changed=XKBCOMMON_NO_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=XKBCOMMON_STATIC
  cargo:rerun-if-env-changed=XKBCOMMON_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR

  --- stderr
  thread 'main' panicked at /home/saadjhk/.cargo/registry/src/index.crates.io-6f17d22bba15001f/smithay-client-toolkit-0.19.2/build.rs:3:49:
  called `Result::unwrap()` on an `Err` value: "\npkg-config exited with status code 1\n> PKG_CONFIG_ALLOW_SYSTEM_LIBS=1 PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags xkbcommon\n\nThe system library `xkbcommon` required by crate `smithay-client-toolkit` was not found.\nThe file `xkbcommon.pc` needs to be installed and the PKG_CONFIG_PATH environment variable must contain its parent directory.\nThe PKG_CONFIG_PATH environment variable is not set.\n\nHINT: if you have installed the library, try setting PKG_CONFIG_PATH to the directory containing `xkbcommon.pc`.\n"
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

OS: Fedora Linux 40
Linux 6.9.12-200.fc40.x86_64
Cargo: 1.80.1 (376290515 2024-07-16)

@mmstick
Copy link
Member

mmstick commented Sep 6, 2024

system library xkbcommon required by crate smithay-client-toolkit was not found

Make sure to install all of the necessary dev dependencies.
You can see what's required in the Build-Depends section in debian/control

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants