Skip to content
This repository has been archived by the owner on Jul 4, 2023. It is now read-only.

FontForge won't compile on 10.8 without the 10.7 SDK #17909

Closed
lilyball opened this issue Feb 17, 2013 · 1 comment
Closed

FontForge won't compile on 10.8 without the 10.7 SDK #17909

lilyball opened this issue Feb 17, 2013 · 1 comment

Comments

@lilyball
Copy link
Contributor

FontForge can't compile on OS X 10.8 if the 10.7 SDK isn't installed. The formula tries to pass the 10.7 SDK path as the -isysroot flag, but without that SDK installed, that just messes things up.
@lilyball
Copy link
Contributor Author

Unfortunately commenting out this line doesn't fix the build, because the build uses FlatCarbon, which is apparently why it wants the 10.7 SDK to begin with. Perhaps it should just throw a friendly error if the 10.7 SDK is missing?

lilyball added a commit to lilyball/homebrew that referenced this issue Feb 17, 2013
@lilyball
Fix FontForge compilation without 10.7 SDK
dec83c1 
FontForge uses the FlatCarbon headers, which are gone in Mountain Lion.
To fix this, the formula was adjusted to use the 10.7 SDK. However, this
prevents compiling FontForge on a system without the 10.7 SDK. Fix this
by replacing the FlatCarbon imports with the correct imports to the
non-flat headers.

Closes Homebrew#17909.
@lilyball lilyball mentioned this issue Feb 17, 2013
Closed
@Homebrew Homebrew locked and limited conversation to collaborators Feb 16, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix FontForge compilation without 10.7 SDK lilyball/homebrew
2 participants
@lilyball @MikeMcQuaid