This requires various changes throughout the build system. Moreover,
the Mac build now works with both Homebrew (in /usr/local/opt) and
MacPorts (/opt/local), but still prefers Homebrew if it is present.

We also adjusted the embed-MacOSX-dependencies.sh script to look for
libquicktime dependents in the right place ($PD_APP_CONTENTS/Plugins),
so that Gem's QT4 plugins will work using the Homebrew libquicktime
package. Alas, MacPorts doesn't have a working libquicktime package, so
the QT4 plugins are disabled there.

Note that setting the fluidsynth log callbacks doesn't help with these
messages, thus we have to resort to the rather drastic method of temporarily
redirecting stderr to /dev/null.

fluid~: Get rid of the custom settings except gain, better to use the fluidsynth defaults in most cases.

As discussed on the mailing list, it's useful to allow symbol
inputs (other than bang) on pddplink's inlet, to make it easier to
invoke pddplink on a variable symbol (filename, patch, URL) value.

Note that for backward compatibility, a dummy filename argument is still
needed. Please check the updated help patch for details and an example.

This is needed to make builds on Arch work again.

Disable zexy/lpt on Windows for now, it doesn't work there at present and causes a segfault in the regression tests.

This adds support for the SMMF MIDI message format,
cf. https://bitbucket.org/agraef/pd-smmf.

It also adds canvas/path search for soundfont files, so that these can
be found more easily without having to use absolute pathnames, as well
as a few cosmetic changes to help and error messages.

In default "legacy" mode, the object is 100% backwards-compatible
(except for the soundfont file search), so that existing patches will
continue to work without any changes.

In SMMF mode, which is invoked with the new -smmf option (used either as
a creation argument, or with the "init" message), the SMMF message
format can be used to denote MIDI messages. Legacy messages still
continue to work in SMMF mode as well, except the "note" and "bend"
messages which are used in both formats with the same argument count but
different argument order. However, the corresponding shortcuts "n" and
"b" of the legacy format still work even in SMMF mode.

Rationale: SMMF offers the following advantages over the legacy message
interface that fluid~ currently uses:

- It covers all MIDI voice messages, as well as system exclusive
  messages. (Note that sysex support is particularly interesting in the
  context of fluidsynth because it allows to pass tuning data using
  sysex messages following the MIDI Tuning Standard (MTS), which
  fluidsynth readily supports.)

- It enforces a close 1-1 correspondence between the Pd MIDI objects and
  the message format (it uses the same basenames as message selectors,
  and has the arguments in the right order to easily interface with the
  Pd MIDI objects).

- It is is readily supported by some helper abstractions (midi-input.pd
  and midi-output.pd, available at https://bitbucket.org/agraef/pd-smmf).

- Last but not least, it is compatible with pd-faust and pd-faustgen2
  which makes it very easy to integrate Faust- and soundfont-based
  synthesis in Pd.

This reverts commit 5eb67db0, reversing
changes made to b363df22.