{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifdcbslhzggpmuddqfaubxbmiuoijwuc5zsmsypaegnoyktx6zboy",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mltmttsvqeq2"
  },
  "path": "/viewtopic.php?t=33412&p=274023#p274023",
  "publishedAt": "2026-05-14T20:08:06.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> Well, you thankfully still can compile PM against GTK2 [...]\n\nI know, it's just a matter of switching 3 for 2 in .mozconfig.  I chose Gtk3 though because it's the native toolkit for the Cinnamon DE I use, and themes for Gtk3 are using a somewhat \"classic\" version of CSS compared to the \"weird\" .rc configuration in Gtk2 themes. I could never get that one right, and as a result the scrollbars in all Gtk2 apps **and** Qt apps that follow the Gtk2 theme, all exhibit an annoying bug. Guess I'll have to fix it at some point, at least for the benefit of Qt apps.\n\n> Yes, Qt5 is mature and stable, whereas Qt6 is still a moving target, with serious issues and incompatibilities between minor releases (e.g. 6.2 vs 6.3) [...]\n\nThat's precisely what I was thinking of. Qt5 is a sure bet, and I believe/hope it will still be for a while. Qt6 is something to look forward to but not bet on, just yet - it might be just too early. Well, just an honest opinion is all. Problem is, for us users of old systems that barely get an early version as backport (Qt 6.2.x), these inconsistencies/incompatibilities between minor versions might be a real show stopper, if developers decide to use incompatible Qt API.\n\n\n**Off-topic:**\n\n\n> For example Ardour [...]\n\nKept seeing people mentioning Ardour on Devuan forums, so I decided to find out what it was. That's exactly how I asked in the search engine: what is Ardour? What do you think the stupid duck answered? A truckload of dictionary definitions explaining what 'ardour' _meant_ in English. But I asked what it **was** , not what it _meant_! Guess it's too subtle of a semantics difference for an \"intelligent\" engine to pick up.\n\nAnyway, I finally found out, went to their git, cloned the repo and then... realized I already had a truckload of dependency packages in some folder, specifically for Ardour, meaning at some point in the past I actually knew about it and wanted to install/test it, or something. Damn short memory of mine!\n\nIn the end I managed to build it succesfully, not before getting awfully mad at the stupid **waf** building system that makes it so damn difficult to provide a simple flag that for some reason was left out of the damn long and convoluted configuration file. It simply needed -std=cxx17 for CXX_FLAGS otherwise it would bail out at about 4-5% in. But before that I got awfully mad at it for the first time when it kept showing missing dependencies _one by one_ instead of all at once, so everytime I installed a missing dependecy and reran the config it was spitting out another missing dependency, and so on and so forth until it drove me close to throwing this notebook out the window. Only close to, thankfully.\n\nBut... what the heck am I going to do with it?! I have no idea whatsoever!\n\n* * *",
  "title": "Browser Development • Re: Linux Pale Moon with Qt toolkit",
  "updatedAt": "2026-05-14T20:08:06.000Z"
}