Post AcLFNAaDSYhwPbOQ0e by hergertme@fosstodon.org
(DIR) More posts by hergertme@fosstodon.org
(DIR) Post #AcJeomjpohvV6YEkGu by charadon@mb.iotib.net
2023-11-30T00:59:14Z
0 likes, 0 repeats
@hergertme@fosstodon.org What kind of black magic have you done where I can use Gnome Builder in the flatpak, and it can STILL use my host packages and compilers?! This is awesome! =D
(DIR) Post #AcLFNAaDSYhwPbOQ0e by hergertme@fosstodon.org
2023-11-30T19:21:55Z
0 likes, 0 repeats
@charadon The very core of Builder was built around a container/runtime design from the beginning. IdeRunContext is the object I added last year which makes that a lot easier to plumb through all the plugins.
(DIR) Post #AcLGriuqTYd1XDAunY by charadon@mb.iotib.net
2023-11-30T19:38:38Z
0 likes, 0 repeats
@hergertme@fosstodon.org That's neat! Reason I called it black magic was because if you compare it to the other flatpak'd IDEs, you have to do a lot of shenanigans with flatpak-spawn --host to get things working correctly. Especially if what you're looking for isn't in the runtime of the IDE's flatpak.In the #Pulsar #Flatpak for example, you have to pretty much modify all your packages to use flatpak-spawn --host before any exec call. Not hard, but definitely annoying!I guess I could make my own runtime, but uh, I don't feel like compiling the equivalent of a Gentoo system. lol
(DIR) Post #AcLHQfnK4ZCjzPK0Qa by hergertme@fosstodon.org
2023-11-30T19:45:20Z
0 likes, 0 repeats
@charadon I use the D-Bus interface instead of flatpak-spawn, because Builder doing this pre-dates flatpak-spawn. So it's not like those IDEs can't do what we do. They just need to be written correctly for a world of containers rather than trying to bolt it on afterwards.
(DIR) Post #AcLKBWcGDPWz2ecFMW by charadon@mb.iotib.net
2023-11-30T20:15:41Z
0 likes, 0 repeats
@hergertme@fosstodon.org What is software, if not a bunch of people bolting things together, eh? lol