ifreund changed the topic of #river to: river - a dynamic tiling wayland compositor || https://github.com/ifreund/river || channel logs: https://libera.irclog.whitequark.org/river/
leon-p has quit [Quit: leaving]
snakedye has quit [Read error: Connection reset by peer]
novakane has joined #river
novakane has quit [Quit: WeeChat 3.2]
novakane has joined #river
novakane has quit [Quit: WeeChat 3.2]
novakane has joined #river
leon-p has joined #river
Guest51 has joined #river
Guest51 has quit [Quit: Client closed]
waleee has joined #river
snakedye has joined #river
leon-p has quit [Quit: leaving]
leon-p has joined #river
wrl has joined #river
novakane has quit [Quit: WeeChat 3.2]
edrex[m] has joined #river
* edrex[m] waves. checking river progress over the summer. getting segfaults shortly after startup. maybe wrong wlroots version? using 0.14.1 from arch. should I be building wlroots like i do for sway? can i symlink it into deps/ or set an env var?
<edrex[m]> i hope @ifreund and @leon-p have had some physical river time too this summer :D
noopdecoder has joined #river
<ifreund> edrex[m]: 0.14.1 should be fine... you sure river and its submodules are up to date?
<ifreund> as for using a non system wide wlroots install, you can set LD_LIBRARY_PATH, C_INCLUDE_PATH, PKG_CONFIG_PATH, etc
<ifreund> just like for any other C library
<edrex[m]> yeah, submodules are up to date. i was just testing plasma, maybe that left the video device in a bad state.
<ifreund> edrex[m]: what does ldd river show?
<ifreund> er, you'd need lld /path/to/river/binary
<ifreund> specifically the wlroots so version should be 9
<edrex[m]> ah. ldd $(which river)|grep wlroots: libwlroots.so.7 => /usr/local/lib/libwlroots.so.7
<edrex[m]> seems i have an old version lying around. i really need to switch my laptop from arch to nixos
<ifreund> yep, that'd do it :/
<ifreund> I should really go make the zig build system handle this better, haven't had the time yet though
<edrex[m]> how do i clean the build?
<ifreund> rm -r ./zig-cache should do it
<edrex[m]> that's what i guessed, should have just tried :)
<edrex[m]> cool, working now :) thx
<ifreund> nice, no problem!
<edrex[m]> seems like the orientation maps and setting/execing the default layout are the only init changes?
<edrex[m]> any config examples using multiple layout gens? curious how that would work
<edrex[m]> nm, i see that isn't the main intented use for layout gens