Improve FONTLOG-related workflow and tooltip
Added typo fix and trailing line fix
Moving FontforgeInternal

Having a directory inside the bin is generally frowned upon, and causes
issues with Homebrew due to our audit red-flagging that behaviour. This
(theoretically) changes that by moving that internal directory to
libexec/bin. This should work okay, theoretically. Let me know what you
all think.
Remove WINDOWS_CROSS_COMPILE

This was only used to avoid a necessary check in collab builds on
Windows. @jtanx, who does the Windows binaries, says collab currently
isn’t building on Windows anyway.
Use libossp-uuid, which works on all platforms

As a result, use UUIDs on Windows
Add ossp-uuid dependency to before_install_osx.sh

Also update an error message in fontforge_arg_with.m4
Fix include path to work irrespective of location of headers
Fix for libossp-uuid installed from source (has different name for pkgconfig)
Adjust all include of uuid.h

And reorder some so that the system-header-defeating code in ossp/uuid.h
can work.

Also ensure that the relevant -I flag is passed everywhere it is needed.
Merge pull request #1838 from DomT4/internalpatch

Moving FontforgeInternal
A few changes to update the PR for changing the location of the
FontForgeInternal directory.

https://github.com/fontforge/fontforge/pull/1838
meta-T on the path max
Rearrange check for blank tooltips

As reported in #1807, for many tooltips, single line tooltips were blank
and the last line of multi-line tooltips were blank.

In an attempt to curb empty tooltips, a change misinterpreted how a
character count was being used.  The value was actually trying to flag
leading lines of a multi-line tooltips.

This change makes that leading/last line flagging a tiny bit more
explicit, adding comments.

Trying to implement the original desire to omit tooltips with empty texts,
this change alters when the loop checks for end-of-string. (do-while
changed to while)  Also, a much earlier check for empty string will
simply exit and not display an empty tooltip text.

In addition to testing normal tooltips (easiest check is hovering over
the checkbox labels in the Generate Fonts dialog; these show two line,
single line, and 11 line tooltips), a series of empty and partially
empty texts were exercised.
```
fontforgeexe/savefontdlg.c
  2611         gcd[k].gd.popup_msg = (unichar_t *) _("Check the glyph outlines for standard errors before saving\nThis can be slow.");

      popup_msg = _("Check the glyph outlines for standard errors before saving\n");
  Shows as correct first line, but then no second line at all - a
    one line tooltip.
  Did GDrawWindowFontMetrics() determine line height to be only one?

      popup_msg = _("\nThis can be slow.");
  Shows as first line blank, second line "This can be slow."

      popup_msg = _("\n");
  A one character blank tooltip is displayed.
    Well, a "\n" sure does say "give me a blank line", so displaying
    *something* seems the correct thing to do.

      popup_msg = _("");
  Nothing is displayed.
```
These special conditions seem to give reasonable results.

This change should close #1807
Merge pull request #1854 from monkeyiq/2014oct/ffidir-fixup1

A few changes to update the PR for changing the location of the FontForgeInternal directory.
Merge pull request #1855 from tshinnic/1807_tooltips_blank_1

Rearrange check for blank tooltips
Use czmq’s own uuid library

This can either use libuuid, Window’s UuidCreate, or its own PRNG.
Update prefs with SnapDistance: 0
Merge pull request #1843 from rrthomas/master

Switch to libossp-uuid, to get UUIDs on Windows
Make the bottom of the horizontal ruler horizontal.
Update prefs SnapDistance: 2