{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreier3re3u7fearu6xj272mdtlhjpp35f7capc467gqtmfkbd6w25sa",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mogkppx2zzp2"
  },
  "path": "/viewtopic.php?t=33537&p=275686#p275686",
  "publishedAt": "2026-06-16T18:28:33.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> Thinking about adding a separate build-time config option for something like --disable-npapi-gtk.\n>\n> The intent here is to separate the NPAPI code in our tree from the GTK supporting code for NPAPI plugins. The idea is that users can continue to run Xlib based NPAPI plugins on Linux distributions where GTK2 is no longer shipped.\n>\n> The pref would be enabled by default so --enable-npapi would build with the GTK2 NPAPI support by default. The user would have to manually pass in --disable-npapi-gtk in mozconfig if they want it disabled.\n>\n> Thoughts? Is this something we want? I have several hours of free time over the next few days so I'll try to implement this if people are interested.\n\nThat would be awesome for me, for building both Basilisk and Pale Moon. Being able to optionally do away with all that code with one .mozconfig line would be great. I haven't used one of those plugins for 15 years probably. But having the code available for people who need it would also be really great.\n\n* * *",
  "title": "Platform Development • Re: Thoughts on splitting out --enable-npapi and gtk?",
  "updatedAt": "2026-06-16T18:28:33.000Z"
}