{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreic7azbcl5to76c5m6lczbamcs2crdjtemsn4iakosvmqhwv5fczye",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mkqdl4jfxea2"
  },
  "path": "/viewtopic.php?t=33365&p=273059#p273059",
  "publishedAt": "2026-04-30T18:56:59.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> Anyways, if you test this: please report any issues you encounter to me.\n> If can make Pale Moon or Basilisk faster by optimising this toolkit then that would be awesome\n\nI got it working and am responding to you from a Basilisk build that is using gtk2-ng right now. The performance is definitely closer to a GTK3 build. All I had to do is set LD_LIBRARY_PATH to the folder where I installed gtk2-ng and it just worked. I didn't modify the build system, it just linked against my system GTK2. So your goal of maintaining ABI compatibility definitely works.\n\nI ran into the issue that gtk2-ng did not include all of the GTK2 theme engines so my OS theme did not work. I'm not sure what the original GTK2 behavior was in this regard. I had to add the directory where my OS package manager has the GTK2 theme engines installed for my theme to the LD_LIBRARY_PATH as well for the theme to work. I did verify that it was still using gtk2-ng after that path to the LD_LIBRARY_PATH to verify that adding that directory didn't break gtk2-ng or cause the build to revert to system GTK2.\n\n* * *",
  "title": "Other/future projects • Re: GTK2 revival",
  "updatedAt": "2026-04-30T18:56:59.000Z"
}