Skip to content
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

Closed
DomT4 opened this issue Dec 31, 2014 · 10 comments
Closed

Building with x11 hardcodes Breakpad #2022

DomT4 opened this issue Dec 31, 2014 · 10 comments

Comments

@DomT4
Copy link
Contributor

DomT4 commented Dec 31, 2014

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 from bin/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 consequently fontforge errors out on dylib not loaded and refuses to load.

You can see this link by executing an otool -L on bin/fontforge.

I used install_name_tool locally to change the @executable_path/../Frameworks/Breakpad.framework/Versions/A/Breakpad link in bin/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 the dylib not loaded fatal run error pops up.

Sorry for the multitude of issues today 😢.

@davelab6
Copy link
Member

@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 :(

@DomT4
Copy link
Contributor Author

DomT4 commented Feb 26, 2015

it means we can't install FontForge with a UI via Homebrew

The UI works, It just needs the install_name_tool fix prior to actually running. We handle it automatically post-install at the moment if you build --with-x11, so it works, It's just not ideal to carry the workaround for an extended period of time. HEAD should be back in Homebrew soon - We're having some issues with the test-bot this evening, but it should be merged within the next 48 hours tops.

@davelab6 davelab6 added this to the 2015-03 Release milestone Mar 9, 2015
@davelab6
Copy link
Member

davelab6 commented Apr 6, 2015

@DomT4 I wonder if this is fixed now - @monkeyiq did a lot of work on the breakpad integration in March

@DomT4
Copy link
Contributor Author

DomT4 commented Apr 6, 2015

I'll remove the old fix and rebuild to see.

@DomT4
Copy link
Contributor Author

DomT4 commented Apr 6, 2015

Yup. Fixed 👍. Looks like the link from bin/fontforge to Breakpad has gone completely.

These are the only otool -L references to Breakpad in the entire tree:

Changing dylib ID of /usr/local/Cellar/fontforge/20150330/share/fontforge/osx/FontForge.app/Contents/Frameworks/Breakpad.framework/Versions/A/Breakpad
  from @executable_path/../Frameworks/Breakpad.framework/Versions/A/Breakpad
    to /usr/local/share/fontforge/osx/FontForge.app/Contents/Frameworks/Breakpad.framework/Versions/A/Breakpad
Changing dylib ID of /usr/local/Cellar/fontforge/20150330/share/fontforge/osx/FontForge.app/Contents/Frameworks/Breakpad.framework/Versions/A/Resources/breakpadUtilities.dylib
  from @executable_path/../Frameworks/Breakpad.framework/Resources/breakpadUtilities.dylib
    to /usr/local/share/fontforge/osx/FontForge.app/Contents/Frameworks/Breakpad.framework/Versions/A/Resources/breakpadUtilities.dylib

@davelab6
Copy link
Member

davelab6 commented Apr 6, 2015

Great! Please close when the brew script is updated in their master :)

@DomT4
Copy link
Contributor Author

DomT4 commented Apr 6, 2015

Just pushing the PR now :).

@davelab6
Copy link
Member

davelab6 commented Apr 6, 2015

🎱

@DomT4
Copy link
Contributor Author

DomT4 commented Apr 6, 2015

Open: Homebrew/legacy-homebrew#38410

tdsmith pushed a commit to Homebrew/legacy-homebrew that referenced this issue Apr 7, 2015
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>
@DomT4
Copy link
Contributor Author

DomT4 commented Apr 7, 2015

Merged!

@DomT4 DomT4 closed this as completed Apr 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants