Adapted for Linux Mint 12

- Updated boost related m4 files with new versions from
  http://www.gnu.org/software/autoconf-archive/index.html
- Platform library needs -lrt to get the symbols timer_create, timer_delete
  and timer_settime.
- Replaced the deprecated av_register_protocol with av_register_protocol2.
- Type of codec_type changed, new enum values.
- Using std::move to pass rvalue reference to StopRecordingSReq constructor.
- Fixed library order passed to linker. High-level libraries must occur in
  front of low-level libraries used by them. autotools are passing LDFLAGS
  in front of LDADD to the linker.
Added configure tests for all linked boost libraries

Copied further m4 scripts from the autoconf-archive:
http://www.gnu.org/software/autoconf-archive/index.html

Further makefile cleanup: LDFLAGS is used for all linker flags except for
linked libraries. LDADD lists all linked libraries, including -l options.
Replaced usage of deprecated FFmpeg interfaces
AlsaFacade: snd_pcm_avail() returns wrong value in state SND_PCM_STATE_XRUN

In ALSA state SND_PCM_STATE_XRUN the audio buffer isn't always indicated
as empty by the snd_pcm_avail() function.
XvPortAttributes are modifiable via a new tab in the ConfigWindow

- Xv API is used in XlibFacade only.
- NotificationVideoAttribute and ChangeVideoAttribute messages are sent
  between GUI and XlibFacade.
VideoAttributeWidget is updated when another application changes Xv attributes

All X11/Xv dependencies are in XlibFacade.*pp.
All Gtk/Gdk dependencies are in gui directory.

GDK Window is used to add a filter function for events from the window.
This is in GtkmmMediPlayer / GtkmmAddGuiEventFilterFunctor.

The filter function itself is X11/Xv specific. It is implemented in
XFVideo / XvGuiEventFilterFunctor.

On the interface between GUI and XFVideo the 2 pure virtual base classes
AddGuiEventFilterFunctor and GuiEventFilterFunctor are used.

To avoid recursion the VideoAttributeWidget does not emit signalVideoAttributeChanged,
when it is updated by a NotificationVideoAttribute signal.
Avoid deadlock when receiving many XvPortNotifyEvent messages

With applications like gxvattr it is possible to modify Xv attributes of
the Xv port used by this player. Moving the sliders in gxvattr quickly
results in many events. A deadlock can occur in Glib::Dispatcher.

Glib::Dispatcher is using a pipe to trigger the GUI thread. Sending many
messages within VideoOutput or from VideoOutput to MediaPlayer results in
sending messages from the GUI thread to the GUI thread. The application
may completely fill the pipe and the write blocks. If it is blocking in
the GUI thread, then a deadlock occurred, since only the GUI thread is
reading from the pipe.

Solution: Writing to the pipe triggers calling the
GtkmmMediaPlayer::processEventQueue method. That method processes all
queued events. The fix is not to write into the pipe when a call to the
method is still pending.
New template class GlibmmEventDispatcher

GlibmmEventDispatcher implements the GUI toolkit specific part to get the
event_processor to process events within the GUI thread. It uses an
atomic_variable to avoid deadlocks when sending many events from the
same thread.

GlibmmEventDispatcher completes the configuration of the event_processor
object used by the base-base class event_receiver.

Class hierarchy is for example:
- event_receiver<MediaPlayer,
                 concurrent_queue<receive_fct_t,
                                  with_callback_function> >
- MediaPlayer
- GlibmmEventDispatcher<MediaPlayer>
- GtkmmMediaPlayer

The MediaPlayer and the GtkmmMediaPlayer classes don't contain any
dispatcher related code, except that the GlibmmEventDispatcher class is
used between both in the class hierarchy.

Note: VideoOutput class is using the same event_processor as MediaPlayer.