<html><head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body> <div class="moz-cite-prefix">On 7/20/21 10:13 AM, Dan Nicholson wrote: </div> <blockquote type="cite" cite="mid:CAJAOzpC2JZ+ED4SxFuzx0n8hQzPqdPLtKD-d=M8HU7MbPmJKwQ@mail.gmail.com"> <pre class="moz-quote-pre" wrap="">The GNOME platform provides libenchant-2, but I imagine you need to provide pyenchant in your application to get the python bindings. Unlike many of the GNOME libraries, enchant's bindings don't come from GObject Introspection, so you don't get python bindings for free from pygobject. -- Dan </pre> </blockquote> Thank you for the information, I will have to look around at what gets bindings and what doesn't. Pygobject and pgi are two more libraries I had to manually add due to Gramps not seeing the Gnome Platform libraries, BTW. Anyways, I didn't know about using pyenchant, which as of version 3.2.1 that I downloaded, includes enchant. That sounds like a better solution than what I was doing. So I installed pyenchant into the flatpak through the manifest, and took out enchant1. Once installed, the Gramps flatpak still can not see enchant according to the Prerequisites Checker add-on. However spell check does work. Anyways, in my github branch as a test I tried adding the following lines to the finish args to make sure that the flatpak could see the Platform: - --filesystem=host - --filesystem=xdg-run/usr/lib/x86_64-linux-gnu/ And I add --exec-prefix=/usr/lib/x86_64-linux-gnu/ to the python3 build command to make sure that Gramps knows where to look for the platform. The flatpak still can't find the Platform once installed. I'm wondering if the links to the platform library from the flatpak get broken after the flatpak exits? --- Scott </body> </html>