Build FontForge git master with Homebrew #1344

davelab6 · 2014-05-05T08:08:08Z

Build FF git master with Homebrew
Send a pull request for the updated fontforge.rb recipe
Set up Travis to ensure we don't break it - http://docs.travis-ci.com/user/osx-ci-environment/
Get the working formula merged into Homebrew upstream
Get the formula to build the FontForge.app bundle so it runs
~~Get Travis CI to push this travis-made FontForge.app bundle to the bigv.io server~~ (cancelled as Travis is too puny)
~~Change "macbook-air-built, macports-based daily build to upload to fuuko" to "macbook-air-built homebrew-based daily build uploaded to bigv"~~ (cancelled as not important)

I am trying to compile FontForge with Homebrew, and the formula hasn't been updated for the bootstrap stuff... any tips? :)

$ brew install --verbose --debug fontforge --HEAD;
...
==> ./autogen.sh
Failed to execute: ./autogen.sh
/usr/local/Library/Homebrew/formula.rb:575:in `system`
BuildError: Failed executing: ./autogen.sh 
1. raise
2. ignore
3. backtrace
4. irb
5. shell
Choose an action: 5
When you exit this shell, you will return to the menu.
$ ./bootstrap;
bootstrap: running: glibtoolize --quiet
bootstrap: warning: No 'git' found; imported gnulib modules may be outdated.
bootstrap: warning: No 'gnulib-tool' found; gnulib modules may be missing.
bootstrap: running: autoreconf --symlink --install
configure.ac:98: installing 'config/ar-lib'
configure.ac:94: installing 'config/compile'
configure.ac:89: installing 'config/config.guess'
configure.ac:89: installing 'config/config.sub'
configure.ac:92: installing 'config/install-sh'
configure.ac:92: installing 'config/missing'
configure.ac:671: error: required file 'lib/Makefile.in' not found
Makefile.am:62: error: required directory ./lib does not exist
Unicode/Makefile.am: installing 'config/depcomp'
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Inputbox.nib/Makefile.am:29: warning: wildcard *.nib: non-POSIX variable name
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Inputbox.nib/Makefile.am:29: (probably a GNU make extension)
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/MainMenu.nib/Makefile.am:29: warning: wildcard *.nib: non-POSIX variable name
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/MainMenu.nib/Makefile.am:29: (probably a GNU make extension)
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Makefile.am:30: warning: wildcard *.cns: non-POSIX variable name
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Makefile.am:30: (probably a GNU make extension)
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Msgbox.nib/Makefile.am:29: warning: wildcard *.nib: non-POSIX variable name
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Msgbox.nib/Makefile.am:29: (probably a GNU make extension)
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/PopUpButton.nib/Makefile.am:29: warning: wildcard *.nib: non-POSIX variable name
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/PopUpButton.nib/Makefile.am:29: (probably a GNU make extension)
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Progressbar.nib/Makefile.am:29: warning: wildcard *.nib: non-POSIX variable name
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Progressbar.nib/Makefile.am:29: (probably a GNU make extension)
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/SecureInputbox.nib/Makefile.am:29: warning: wildcard *.nib: non-POSIX variable name
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/SecureInputbox.nib/Makefile.am:29: (probably a GNU make extension)
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Textbox.nib/Makefile.am:29: warning: wildcard *.nib: non-POSIX variable name
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Textbox.nib/Makefile.am:29: (probably a GNU make extension)
autoreconf: automake failed with exit status: 1

The text was updated successfully, but these errors were encountered:

JoesCat · 2014-05-25T19:57:25Z

Homebrew needs to be updated at approx line 99. See issue #1366

adrientetar · 2014-06-24T16:44:33Z

What's the status of this?

JoesCat · 2014-06-25T03:09:35Z

These should be gone since they are put in the config directory, which
bootstrap seems (hard-coded to use).

configure.ac:89: installing 'config/config.guess'
configure.ac:89: installing 'config/config.sub'

These warning should be gone.

osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Inputbox.nib/Makefile.am:29: 
warning: wildcard *.nib: non-POSIX variable name
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Inputbox.nib/Makefile.am:29: 
(probably a GNU make extension)
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/MainMenu.nib/Makefile.am:29: 
warning: wildcard *.nib: non-POSIX variable name
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/MainMenu.nib/Makefile.am:29: 
(probably a GNU make extension)
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Makefile.am:30: 
warning: wildcard *.cns: non-POSIX variable name
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Makefile.am:30: 
(probably a GNU make extension)
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Msgbox.nib/Makefile.am:29: 
warning: wildcard *.nib: non-POSIX variable name
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Msgbox.nib/Makefile.am:29: 
(probably a GNU make extension)
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/PopUpButton.nib/Makefile.am:29: 
warning: wildcard *.nib: non-POSIX variable name
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/PopUpButton.nib/Makefile.am:29: 
(probably a GNU make extension)
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Progressbar.nib/Makefile.am:29: 
warning: wildcard *.nib: non-POSIX variable name
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Progressbar.nib/Makefile.am:29: 
(probably a GNU make extension)
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/SecureInputbox.nib/Makefile.am:29: 
warning: wildcard *.nib: non-POSIX variable name
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/SecureInputbox.nib/Makefile.am:29: 
(probably a GNU make extension)
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Textbox.nib/Makefile.am:29: 
warning: wildcard *.nib: non-POSIX variable name
osx/FontForge.app/Contents/MacOS/CocoaDialog.app/Contents/Resources/Textbox.nib/Makefile.am:29: 
(probably a GNU make extension)

As for the homebrew formula, a suggestion has been posted in #1366 which
should work, and the OP of #1366 indicated it does work.
I suggest someone running a MAC needs to triage the solution to confirm it
does works, and after it is confirmed, follow-up with homebrew to update
fontforge.rb

NOTE the ./bootstrap and ./autogen.sh (homebrew if/then/else) is a seperate
issue from python-dev which still needs to be hardcoded to stop since the
warning is quietly ignored by homebrew.

davelab6 · 2014-07-24T04:52:07Z

@monkeyiq please look into this :)

monkeyiq · 2014-07-28T22:59:56Z

A few general "brew" questions. For me the above brew install line from Dave's original post tries to build without using X. This may be that my brew is set to not use X? If I use the below then I get a GUI:

brew install --verbose --debug fontforge --HEAD --with-x

And is there anything needed to 'select' the python that brew has installed. By default fontforge doesn't find that python's pc file so will fail to build. I have a work around for that, but thought I'd ask in case there is already some work around in brew. As brew seems to set PKG_CONFIG_PATH to various subdirectories for you, but not the python one.

davelab6 · 2014-07-28T23:12:18Z

Did you look at Homebrew/legacy-homebrew#27221 ?

I think if you have done 'brew install python' already then the build will find the pc files.

Do you have this, https://github.com/Homebrew/homebrew/wiki/Homebrew-and-Python#technical-details ?

monkeyiq · 2014-07-29T05:39:08Z

Hmm adding some python deps to the brew file doesn't seem to resolve things right off the bat. I notice that python-config is then in the path and might work, but fontforge looks to use pkg-config to do the magic. I'll have a look at a work around.

BuildError: Failed executing: ./configure --prefix=/usr/local/Cellar/fontforge/HEAD --enable-double --without-freetype-bytecode --with-static-imagelibs --enable-pyextension
4. shell
Choose an action: 4

bash-3.2$ pkg-config --list-all |grep -i py
xpyb                                XPyB - X-protocol Python Binding
bash-3.2$ python-config --cflags
-I/usr/local/Cellar/python/2.7.8/Frameworks/P

monkeyiq · 2014-07-29T10:31:06Z

ok I have something for the python issue now. next up is to fix that git/gnulib issue (top post) in a more permanent way.

davelab6 · 2014-07-29T22:01:32Z

AHA!! :) http://docs.travis-ci.com/user/osx-ci-environment/

We can now test that FontForge builds with HomeBrew for each pull request via Travis!!

davelab6 · 2014-07-29T22:08:44Z

I updated the top of the issue to list out the goals

monkeyiq · 2014-07-30T00:28:08Z

Still need to fix something in fontforge.rb

monkeyiq · 2014-07-30T01:00:33Z

@dave does it build for you now using Homebrew/legacy-homebrew#31226

monkeyiq · 2014-07-31T01:05:04Z

Current Pull Request for point #2 is at Homebrew/legacy-homebrew#31226

davelab6 · 2014-08-06T22:38:19Z

@monkeyiq yes, that :) Found a small bug with the About window, will report a new issue for it.

davelab6 · 2014-09-22T17:31:28Z

@monkeyiq is the working formula merged into Homebrew upstream?

And does the formula now build the FontForge.app bundle?

DomT4 · 2014-09-22T18:15:25Z

@davelab6 Looks like it was merged in this commit.

And yes, an app bundle is being built, but isn't symlinked into /Applications due to the slightly unusual placement of that app bundle.

DomT4 · 2014-09-22T23:18:32Z

In fact, symlinking into ~/Applications doesn't work at all. Fontforge refuses to launch from the .app bundle compiled from source. Hmm. The only way to launch it is to execute fontforge in your terminal application which causes X11 and Fontforge to spring open.

davelab6 · 2014-09-22T23:30:32Z

The bundle needs to be in /Applications.

DomT4 · 2014-09-22T23:33:12Z

Homebrew doesn't directly install anything into /Applications. It symlinks from {prefix} into /Applications. That Fontforge symlink into /Applications doesn't work. If Fontforge is configured to absolutely require a solid, non-symlinked bundle in /Applications it'll never work in that way through Homebrew. I'll double check the --HEAD build in a moment, but I think it's the same deal.

davelab6 · 2014-10-03T15:19:56Z

HB can build a FontForge bundle in ~/Appplications and when the user runs it, it will say 'move me to /Applications' and quit. Will that be ok?

davelab6 · 2014-10-03T15:20:48Z

@monkeyiq there are 2 oustanding tasks in the top:

Get the formula to build the FontForge.app bundle so it runs
Get Travis CI to push this travis-made FontForge.app bundle to the bigv.io server

Are those done?

DomT4 · 2014-10-03T18:12:22Z

We don't directly build anything in /Applications. Even Homebrew-Cask doesn't directly install there. Everything is done via symlinks, ie, in this case we'd move the app bundle out of its current prefix & into the main installation folder (In this case, usually /usr/local/cellar/fontforge and then symlink from there into /Applications. If you can get that setup to work with the message that the bundle itself should be moved to /Applications Homebrew can't nullify that suggestion.

davelab6 · 2014-10-16T13:11:15Z

It doesn't work symlinked today:

However, if I remove the check at https://github.com/fontforge/fontforge/blob/master/osx/FontForge.app/Contents/MacOS/FontForge#L13-L23 :

# $0 is possibly relative path to this script.
SCRIPT_PATH="$( cd "$( dirname "$0" )" && pwd )"
PKGBASEPATH="$( cd "${SCRIPT_PATH}/../.." && pwd )"

echo "PKGBASE: $PKGBASEPATH"
if [ y"$PKGBASEPATH" != "y/Applications/FontForge.app" ]; then
  COCOA_DIALOG="${SCRIPT_PATH}/CocoaDialog.app/Contents/MacOS/CocoaDialog";
  $COCOA_DIALOG msgbox --no-newline \
    --title "FontForge: Error starting" \
    --text "FontForge is in the wrong folder on your computer." \
    --informative-text "Please ensure that the FontForge.app directory is directly inside your /Applications folder." \
    --button1 "OK" --float
    BASEPATH="$( cd "${PKGBASEPATH}/.." && pwd )"
    open "$BASEPATH"
    exit;
fi

it runs!

So @monkeyiq please update the check so that if you move the app to /tmp and symlink it, it passes this shell script test. Then I hope @DomT4 can adjust the homebrew receipe to symlink to the app bundle it builds in /usr/local/cellar/fontforge

davelab6 · 2014-10-17T05:14:01Z

@DomT4 good news, @monkeyiq has made the change - https://github.com/fontforge/fontforge/pull/1808/files#diff-0

monkeyiq · 2014-10-17T06:20:25Z

This and an earlier issue are in 201410/17_1506

davelab6 · 2014-10-17T19:46:37Z

@monkeyiq but I think @DomT4 can not build his own package to get to this step :(

DomT4 · 2014-10-17T22:23:06Z

Then I hope @DomT4 can adjust the homebrew receipe to symlink to the app bundle it builds in /usr/local/cellar/fontforge

Yup. This is easily enough done once we get a successful build inside Homebrew.

davelab6 · 2014-10-22T22:36:59Z

@DomT4 do we now have a successful build?

DomT4 · 2014-10-22T23:44:04Z

@davelab6 Yup. I've had to temporarily kill off the colab elements, see #1837, but we're good to go on moving forwards without those for now.

davelab6 · 2014-10-23T00:33:14Z

Okay great! So the remaining task on this issue is for @monkeyiq to change from a "macbook-air-built, macports-based daily build to upload to fuuko" to "macbook-air-built homebrew-based daily build uploaded to bigv"

This should help to ensure that we keep brew install fontforge --HEAD working at all times.

DomT4 · 2014-10-23T00:39:07Z

For any urgent fixes, ie fixing the dylib issue, fixing the issue in #1838, etc I'll very probably port those backwards to the stable build in Homebrew. Just shout if you need anything and I'll do my best.

davelab6 · 2014-10-23T09:51:05Z

Nah, lets just make a new release next week

DomT4 · 2014-10-23T16:05:34Z

Alright, Will keep an eye out. I'll keep fingers crossed the dylib issue is solved by that point and I can turn collab back on by default, but if a week is too soon I'll just leave that out as an option instead again.

davelab6 · 2014-10-27T20:20:22Z

@DomT4 dynlib is solve :)

DomT4 · 2014-10-27T20:25:18Z

@davelab6 Cheers Dave. I could use a release here to nicely wrap up all the changes made in the last week or so if possible? There's probably way too much to backport at this point without ensuring nobody ever wants to maintain the Homebrew formula ever again, heh.

adrientetar · 2014-10-27T20:29:09Z

Travis OS X still fails FWIW… e.g. https://travis-ci.org/fontforge/fontforge/jobs/39176945

DomT4 · 2014-10-27T20:32:23Z

^^ It appears to ship 4 dependencies that Homebrew's formula doesn't. Is that an issue?

The Travis build is waaaay behind Homebrew's though, even with your custom modifications to make life easier on Travis the script it is using is at least 2 or 3 versions behind Homebrew's.

DomT4 · 2014-10-27T20:41:56Z

The current Homebrew formula with the current Fontforge git head works:

==> Summary
🍺  /usr/local/Cellar/fontforge/HEAD: 1278 files, 39M, built in 7.9 minutes

davelab6 · 2014-10-28T07:29:36Z

I think Travis installs their own easy_install and pip, so its failing on brew install python...

DomT4 · 2014-10-28T17:49:49Z

If Python is already on the system and stored in /usr/bin or /usr/local/bin you should be able to trim the Python dependency from the formula and make it pass Travis that way.

davelab6 · 2014-10-28T18:00:22Z

But will ff python work that way?
On 28 Oct 2014 23:19, "Dominyk Tiller" notifications@github.com wrote:

If Python is already on the system and stored in /usr/bin or
/usr/local/bin you should be able to trim the Python dependency from the
formula and make it pass Travis that way.

—
Reply to this email directly or view it on GitHub
#1344 (comment)
.

DomT4 · 2014-10-28T20:52:45Z

Should do, if you're building from source each time. It might be worth passing the --build-from-source flag to Travis for the Homebrew build of Fontforge. I believe source builds can use the system Python just fine without having to specify a Python dependency in the formula.

davelab6 added the question label May 5, 2014

JoesCat mentioned this issue Jun 20, 2014

Test for headers and library for FONTFORGE_ARG_WITH_LIBPNG() #1432

Merged

adrientetar added packaging and removed question labels Jul 24, 2014

davelab6 mentioned this issue Jul 29, 2014

Installing fontforge for use in metapolator #1366

Closed

monkeyiq mentioned this issue Jul 30, 2014

issue1344: work on source tree clones from bootstrap. #1590

Merged

davelab6 mentioned this issue Aug 6, 2014

About window line wrapping problem (Homebrew built) #1628

Closed

frank-trampe mentioned this issue Aug 7, 2014

Document the package build process and make a release #1469

Closed

23 tasks

davelab6 assigned monkeyiq Oct 3, 2014

davelab6 mentioned this issue Oct 27, 2014

Updating travis-scripts/fontforge.rb #1870

Merged

davelab6 closed this as completed Nov 27, 2014

Build FontForge git master with Homebrew #1344

Build FontForge git master with Homebrew #1344

Comments

davelab6 commented May 5, 2014

JoesCat commented May 25, 2014

adrientetar commented Jun 24, 2014

JoesCat commented Jun 25, 2014

davelab6 commented Jul 24, 2014

monkeyiq commented Jul 28, 2014

davelab6 commented Jul 28, 2014

monkeyiq commented Jul 29, 2014

monkeyiq commented Jul 29, 2014

davelab6 commented Jul 29, 2014

davelab6 commented Jul 29, 2014

monkeyiq commented Jul 30, 2014

monkeyiq commented Jul 30, 2014

monkeyiq commented Jul 31, 2014

davelab6 commented Aug 6, 2014

davelab6 commented Sep 22, 2014

DomT4 commented Sep 22, 2014

DomT4 commented Sep 22, 2014

davelab6 commented Sep 22, 2014

DomT4 commented Sep 22, 2014

davelab6 commented Oct 3, 2014

davelab6 commented Oct 3, 2014

DomT4 commented Oct 3, 2014

davelab6 commented Oct 16, 2014

davelab6 commented Oct 17, 2014

monkeyiq commented Oct 17, 2014

davelab6 commented Oct 17, 2014

DomT4 commented Oct 17, 2014

davelab6 commented Oct 22, 2014

DomT4 commented Oct 22, 2014

davelab6 commented Oct 23, 2014

DomT4 commented Oct 23, 2014

davelab6 commented Oct 23, 2014

DomT4 commented Oct 23, 2014

davelab6 commented Oct 27, 2014

DomT4 commented Oct 27, 2014

adrientetar commented Oct 27, 2014

DomT4 commented Oct 27, 2014

DomT4 commented Oct 27, 2014

davelab6 commented Oct 28, 2014

DomT4 commented Oct 28, 2014

davelab6 commented Oct 28, 2014

DomT4 commented Oct 28, 2014