You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It used to work fine, but I got a newer Mountain Lion Mac and tried to install the python extension of fontforge. First, I installed fontforge using macports, but then deactivated it, because I had forgotten to install XQuartz first. Then when I tried using macports version of fontforge @20120731_3+freetype_bytecode+python27, it complained about "SystemError: No initialization function in fontforge library".
So, I tried building fontforge from source, as I've done in the past, but unlike the past, it didn't try to install the extension into /opt/local/lib, though I used the PKG_CONFIG_PATH variable and --with-python-binary switches. The build put the extension into /usr/local/lib. Didn't seem like a good idea to mix ports and non-ports anyway, so I built a new python from source and installed into /usr/local. Then I configured fontforge to point at my new python install:
So looks like it's trying to access an object that's null. Here is a listing of the object that's getting passed into the depths of Python, where I don't have debugging symbols enabled. I can't tell if it's ok or not, but hoping someone on the list can tell:
The text was updated successfully, but these errors were encountered: