Yeah, Oliver, your email just nudged me over the boundary. I think I'll just statically link libGL to the main (virtual machine) process each and every time. This is terrible because now CLI programs need libGL!
Jesus, mono-cycling down a road drunk, christ! This also open up some potential serious annoyances ie non-nixos installations of nix and libgl... I quiver in fear. /sjm On Wed, Mar 2, 2016 at 4:56 AM, Oliver Charles <[email protected]> wrote: > The only way I've had luck with NixOS and OpenGL in the past is by building > anything that needs OpenGL against the same set of nixpkgs that the system > is currently *running* as. Maybe that will help? > > On Tue, Mar 1, 2016 at 5:01 PM stewart mackenzie <[email protected]> wrote: >> >> Hi Herwig, >> >> Okay, Herwg, this is what's driving me insane: >> >> https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/libraries/mesa/default.nix#L27 >> >> Yes, I do not want to link to the stock nix libGL because it has >> STATIC_TLS enabled without which would result in a 10% performance >> hit. So if you're playing hardcore games you want STATIC_TLS. >> >> I on the other hand do not want STATIC_TLS because if I have it >> enabled it throws this error ""SDL error: Failed loading libGL.so.1: >> dlopen: cannot load any more object with static TLS"', hence I need to >> recompile it ensuring no initial-exec (which == STATIC_TLS) is >> enabled. >> >> As I'm running a simple 2D windowing system (conrod) it's more than >> adequate for my needs. >> >> Excellent, much appreciated Herwig. >> _______________________________________________ >> nix-dev mailing list >> [email protected] >> http://lists.science.uu.nl/mailman/listinfo/nix-dev _______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
