-
Notifications
You must be signed in to change notification settings - Fork 27
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
Problems building and launching RS3 on NixOS? #51
Comments
RS3 has barely any built in debug information as far as I know. Anything useful is likely to be in stdout. (i.e. run |
Damn, thanks though. When I try to build it myself (not through Flatpak) I get a bunch of linker errors coming from CEF (I think it's because the directory structure is so different on Nix) |
I know someone I could ask. What errors do you get? |
My steps:
Errors
|
Those first few lines look very much like the list of dependencies for the AUR package: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=bolt-launcher#n9 You might have to track all of these down. |
I was able to follow those dependencies and install them all via |
Nevertheless, it would still be very useful if you could indeed show me how your acquaintance does it on nix :D |
libcef doesn't have a way to search for its dependencies. I guess it just expects them to be in your search path. You'd have to do what it says and patch libcef.so using |
Will try. In the above scenario it would be easy to package it as a nixpkg or in other package managers |
Pre-built binaries for x86_64 and aarch64 is what flatpak is for. A standalone binary would not work for NixOS unless it was built on the exact same commit of nixpkgs as you're currently using (not factoring in overlays etc). If Bolt was packaged on nixpkgs it wouldn't be as simple as just the binary; it would be the process that you're currently doing, but automated. For example, you can see the Google Chrome package doing a quite similar process. |
FYI, I downgraded the Bolt flatpak to v0.8.2 and RS3 launches correctly now. I assume it has something to do with Nvidia drivers not matching in the Flatpak since the pure RS3 flatpak did launch correctly. I'll try to find some time to figure out what the breaking change was between 0.8.2 and 0.9 |
I'm having the same problem. I use NixOS as well. How did you downgrade? |
I think I looked for the previous version commit and used that in the flatpak install command. |
Hey, If anybody wants to run Bolt Launcher on NixOS, I have successfully built a working derivation that should be merged into nixpkgs (track NixOS/nixpkgs#338470). I've added it to my dotfiles in the meantime for conveniency, so you can add something like: home.packages = [
inputs.nezia-dotfiles.packages.bolt-launcher
]; to your dotfiles, with my flake as an input: nezia-dotfiles = {
url = "github:nezia1/flocon";
inputs.nixpkgs.follows = "nixpkgs";
}; Let me know how it goes! I'd appreciate feedback, especially on RS3 since I haven't tried it yet (I mostly play OSRS). |
Using Flatpak on NixOs I manage to get the Bolt launcher running. RuneLite works well, but the rs3 doesn't:
I would like to debug this, but cannot find any crash logs whatsoever. Is this not a thing? Or are they somewhere stored through Bolt?
Thanks!
The text was updated successfully, but these errors were encountered: