Way Cooler/way-cooler

Customizable Wayland compositor (window manager) written in Rust

Uli Schlachter

@psychon

mkdir build && cd build && meson .. && ninja just finished without problems

Preston Carpenter

@Timidger

Ok so it's a different problem. Must not have the right include flags

Check build.rs in wlroots-sys

Uli Schlachter

@psychon

here's the complete output:

   Compiling wlroots-sys v0.0.0 (file:///home/psychon/projects/way-cooler/wlroots-rs/wlroots-sys)
error: failed to run custom build command for `wlroots-sys v0.0.0 (file:///home/psychon/projects/way-cooler/wlroots-rs/wlroots-sys)`
process didn't exit successfully: `/home/psychon/projects/way-cooler/target/debug/build/wlroots-sys-8cd72f8004bc80ce/build-script-build` (exit code: 101)
--- stdout
cargo:rustc-link-search=native=wlroots
cargo:rustc-link-search=native=/home/psychon/projects/way-cooler/target/debug/build/wlroots-sys-602c5290173c60b1/out/lib
cargo:rustc-link-search=native=/home/psychon/projects/way-cooler/target/debug/build/wlroots-sys-602c5290173c60b1/out/lib64
cargo:rustc-link-search=native=/home/psychon/projects/way-cooler/target/debug/build/wlroots-sys-602c5290173c60b1/out/build/
cargo:rustc-link-search=native=/home/psychon/projects/way-cooler/target/debug/build/wlroots-sys-602c5290173c60b1/out/util/
cargo:rustc-link-search=native=/home/psychon/projects/way-cooler/target/debug/build/wlroots-sys-602c5290173c60b1/out/types/
cargo:rustc-link-search=native=/home/psychon/projects/way-cooler/target/debug/build/wlroots-sys-602c5290173c60b1/out/protocol/
cargo:rustc-link-search=native=/home/psychon/projects/way-cooler/target/debug/build/wlroots-sys-602c5290173c60b1/out/xcursor/
cargo:rustc-link-search=native=/home/psychon/projects/way-cooler/target/debug/build/wlroots-sys-602c5290173c60b1/out/xwayland/
cargo:rustc-link-search=native=/home/psychon/projects/way-cooler/target/debug/build/wlroots-sys-602c5290173c60b1/out/backend/
cargo:rustc-link-search=native=/home/psychon/projects/way-cooler/target/debug/build/wlroots-sys-602c5290173c60b1/out/render/
cargo:rustc-link-lib=static=wlr_util
cargo:rustc-link-lib=static=wlr_types
cargo:rustc-link-lib=static=wlr_xcursor
cargo:rustc-link-lib=static=wlr_xwayland
cargo:rustc-link-lib=static=wlr_backend
cargo:rustc-link-lib=static=wlr_render
cargo:rustc-link-lib=static=wl_protos
ninja: no work to do.
/usr/include/x86_64-linux-gnu/sys/types.h:145:10: fatal error: 'stddef.h' file not found, err: true

--- stderr
/usr/include/x86_64-linux-gnu/sys/types.h:145:10: fatal error: 'stddef.h' file not found
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ()', src/libcore/result.rs:916:5
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::begin_panic
   6: std::panicking::begin_panic_fmt
   7: rust_begin_unwind
   8: core::panicking::panic_fmt
   9: core::result::unwrap_failed
             at src/libcore/macros.rs:23
  10: <core::result::Result<T, E>>::unwrap
             at src/libcore/result.rs:782
  11: build_script_build::main
             at wlroots-rs/wlroots-sys/build.rs:17
  12: std::rt::lang_start::{{closure}}
             at src/libstd/rt.rs:74
  13: std::panicking::try::do_call
  14: __rust_maybe_catch_panic
  15: std::rt::lang_start_internal
  16: std::rt::lang_start
             at src/libstd/rt.rs:74
  17: main
  18: __libc_start_main
  19: _start

I briefly tried to figure out what build-script-build is and... dunno

Preston Carpenter

@Timidger

https://askubuntu.com/q/390805/155374?

Could this be the problem?

Uli Schlachter

@psychon

according to find, I have stddef.h from linux headers, clang and gcc (three versions from gcc?!?)

what I do not have is clang itself (as in, /usr/bin/clang)

time for strace...

it's looking for stddef.h in lots of funny places (and even once finds GCC's version)

http://ix.io/17KT

Preston Carpenter

@Timidger

It sounds like you need to either fix your header installs or patch build.rs to have the necessary -I flag so that it can find stddef.h. From googling this seems like Ubuntu's problem though, I have no problem building this on arch

Uli Schlachter

@psychon

hm, this is trying to run llvm-config --prefix, but fails since there is no such program

but installing that did not help

Preston Carpenter

@Timidger

As a temporary work around, you can install wlroots and when building wlroots-rs you can specify no default features to get dynamic linking to the .so

Uli Schlachter

@psychon

so far I'm not happy with that solution, but yeah :-)

Preston Carpenter

@Timidger

I believe that is exposed in Way Cooler as well as a feature flag. If it is not, feel free to make that modification and open a pr

Hopefully the problem can be fixed later

Uli Schlachter

@psychon

do you know what this build-script-build is? It seems to be a compiled version of build.rs....

Preston Carpenter

@Timidger

Yes that is what it is referring to

Uli Schlachter

@psychon

okay, then I can do a hacky solution, even though I still do not understand why this issue occurs

Preston Carpenter

@Timidger

Particularly because the line numbers it gives refers to the build script in wlroots-sys

:+1:

Uli Schlachter

@psychon

oh, right

the following patch for wlroots-sys (which is of course a bad thing to do) makes things build here:

diff --git a/wlroots-sys/build.rs b/wlroots-sys/build.rs
index f177ef0..7d15561 100644
--- a/wlroots-sys/build.rs
+++ b/wlroots-sys/build.rs
@@ -28,6 +28,7 @@ fn main() {
         .ctypes_prefix("libc")
         .clang_arg("-Iwlroots/include")
         .clang_arg("-Iwlroots/include/wlr")
+        .clang_arg("-I/usr/lib/llvm-4.0/lib/clang/4.0.1/include")
         // NOTE Necessary because they use the out directory to put
         // pragma information on what features are available in a header file
         // titled "config.h"

okay, wlroots-sys builds, now I have to wait for rustc 1.25 in debian testing before I can build wlroots-rs

Preston Carpenter

@Timidger

Haha glad it works but yeah best not to have that in upstream. Surely there's a sym link somewhere to that.

I suggest using rustup to install rust

In the future I'm going to make a better rust version guarantee. Eh pin it to an epoch or something

Uli Schlachter

@psychon

I like debian-managed installations of stuff

and for religious reasons I cannot pipe the output of curl into a shell....

Preston Carpenter

@Timidger

Fair enough haha

Uli Schlachter

@psychon

...which is hard to read, does complicated stuff and in the end just downloads an ELF file from the internet and runs it without any verification or integrety checks

and that binary most likely is not even distributable; it seems to contain a static copy of openssl (according to /usr/bin/strings)

and GPL-wise, I see no offer/way to get to the source of that binary</rant>

Preston Carpenter

@Timidger

I'm not a fan of the distribution model either, but it's the easiest way for me to have the latest rust. But that would be fixed by just not requiring the latest rust I suppose ;-).

I'll pin it when they release their first epoch, if only so you don't need that to use rustup (and for people wanting to build it on non rolling release / test distros)

Uli Schlachter

@psychon

what distro are you using? arch?

also, I gotta go, bye & have a nice evening (afternoon?)

Preston Carpenter

@Timidger

Yep arch

You too!

(that's also what the build server runs)

Uli Schlachter

@psychon

I installed rustc 1.25 from debian experimental and now linking fails, because libcap and libsystemd are not found

...which makes me wonder why they are required in the first place, but I'll investigate that tomorrow

oh, just removing the relevant lines from wlroots-sys/build.rs seems to do the trick (wlroots itself already noticed that these libraries are unavailable and did not try to use them)

Preston Carpenter

@Timidger

Probably both optional wlroots dependencies I didn't express correctly. Patches welcome!

Uli Schlachter

@psychon

I looked at it and... well, wlroots automatically uses these dependencies if they are available. However, I found no sane way to figure out if they were found or not. Basically, static linking is bad. I will just ignore this issue for now.

Uli Schlachter

@psychon

since you are not in #awesome, I'll report here: I kind-of managed to do a non-static build of way-cooler; ninja install does not install all required headers for wlroots and so build.rs still needed to be pointed at some source directory; besides that, this worked

then I was staring at stuff and now I switched to gaming ;-)

Where communities thrive

People

Repo info

Activity