New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building with x11 hardcodes Breakpad #2022
Comments
@monkeyiq yikes - this is pretty urgent, it means we can't install FontForge with a UI via Homebrew, and since your fuuko package builder is down, we are totally without a way to run HEAD on Mac :( |
The UI works, It just needs the |
I'll remove the old fix and rebuild to see. |
Yup. Fixed 👍. Looks like the link from These are the only
|
Great! Please close when the brew script is updated in their master :) |
Just pushing the PR now :). |
🎱 |
The install-name error was rectified by the latest release and the whole post-install block can be killed. Yay! Note to self: When merged close fontforge/fontforge#2022. Closes #38410. Signed-off-by: Tim D. Smith <git@tim-smith.us>
Merged! |
Building Fontforge (either the git tag or the archive tarball; haven't tried the release tarball yet because of the errors I discussed in the other issue) with
x11
support enabled seems to generate a hardcoded link frombin/fontforge
to@executable_path/../Frameworks/Breakpad.framework/Versions/A/Breakpad
, the latter of which obviously doesn't exist in the situation where the binary is separate from the app bundle, and consequentlyfontforge
errors out ondylib not loaded
and refuses to load.You can see this link by executing an
otool -L
onbin/fontforge
.I used
install_name_tool
locally to change the@executable_path/../Frameworks/Breakpad.framework/Versions/A/Breakpad
link inbin/fontforge
to the share directory where FontForge.app exists, which fixed the error.I'm not explicitly requesting Breakpad to build, although I'd be happy for it to do so, but if I build
--with-x
I get it regardless and when run thedylib not loaded
fatal run error pops up.Sorry for the multitude of issues today 😢.
The text was updated successfully, but these errors were encountered: