Be more stringent on what it means to be tightly-coupled for two layouts.

Note that directly resizing a playout should not be allowed. Only the skins2
windows manager should be authorized to do it, since other issues are at stake
(anchors, min/max constraints, ....). Yet, this new isTightlyCoupledWith() now
ensures that two layouts are truly identical from the windows manager's
perspective, and thus avoids possible and undesirable side effects.

The latest automake versions (as built by extras/tools) have
removed support for ansi2knr altogether, so this is required for
reconfiguration to work. We still need to do the reconf since the
host system ANSI check in the tarball is broken.
Signed-off-by: Martin Storsjö <martin@martin.st>

This is required for detecting ar and ranlib properly, required
e.g. when cross compiling for android from OS X.

One can't set CMAKE_AR or CMAKE_RANLIB directly. Normally they
should be set properly automatically within cmake, but those
codepaths seem to be skipped when we set the C/CXX compilers
manually.
Signed-off-by: Martin Storsjö <martin@martin.st>

This fixes cross compilation from OS X.
Modified-by: Rafaël Carré <funman@videolan.org>
Signed-off-by: Rafaël Carré <funman@videolan.org>

Most distributions have fonts in paths different from defaults.
Signed-off-by: Rafaël Carré <funman@videolan.org>

AF_INET is defined in sys/socket.h
Signed-off-by: Rafaël Carré <funman@videolan.org>

Certain skins like wmp12 may fail to deal with video controls in some
corner cases. For this skin, no window was set visible and the skin
engine eventually fell back to force the first window to become visible.

This patch is expected to fix trac #8368 (need to be tested on windows)

They did not respect the naming convention (in the include files - the
implementation ones are already correct).

The brackets in the config test aren't properly escaped, and thus
don't end up in the final configure script as intended.

When building on a system where the system default compiler is clang,
clang can fail due to the main signature
"int main(int argc, char *argv)" being invalid,
which makes configure believe that the system compiler isn't
ANSI compliant, and it tries to invoke (broken) ANSI2KNR code.
Signed-off-by: Martin Storsjö <martin@martin.st>

Signed-off-by: Martin Storsjö <martin@martin.st>

So far, the RGBA shader has only been used for the subpictures.
On ES2, the fixed function pipeline is not available, so we need to
use the shader for drawing the main picture even if it is RGBA.
Signed-off-by: Martin Storsjö <martin@martin.st>

http intf: Manage Streams: Create Mosaic: Capitalize first letter, remove : in the first column. All except 'Row/Column Border' occur at different places as well
Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>

Typo: Remove leading space in about-box, use I_PL_ADDPL(=Add to Playlist) for Add to playlist. Use identical sentence (only differs by -)
Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>

Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>

and simplify the code a bit for better readability

Handle better cases when we don't have input frame size
same as encoder input frame size. Also gather input samples
untill we get full frame fillet and not just next block.

Set length based on used samples and not frame_size

Also try to make memory calculations cleaner so they don't
overshoot and write stuff all over.

Refs #8265

In the Web documentation, it reads "text automatically starts scrolling" in automatic mode.

This vout uses ES2, not ES1. The right headers are included by
opengl.h anyway, this was just confusing and wrong.
Signed-off-by: Martin Storsjö <martin@martin.st>

This avoids doing the intermediate copy in some cases.
Signed-off-by: Martin Storsjö <martin@martin.st>

This is the actual width used in the upload calls if the check
matched, so this is the width we should check for.
Signed-off-by: Martin Storsjö <martin@martin.st>

This fixes a regression brought by ff74e967

Forcefully resizing only makes sense when layouts were designed to be similar
in size in the first place. Furthermore, it cuts off a larger layout if a
smaller one is first defined when loading a skin.

Ideally, the skins2 dtd should be extended for skins developers to explicitly
express whether two layouts are tightly-coupled or not, i.e should always be
kept the same size whatever the subsequent resizing performed by the user.

In skins2, a window can have multiple layouts with two different goals.

First goal, layouts have the same original size and only differ in the
presentation (different color, ...). If the active layout gets resized,
the user expects the related inactive layouts with the same size to
automatically resize, should they become active.

Second goal, layouts are different in size, e.g a reduced layout and an
expanded layout. In this case, resizing the active layout doesn't mean
resizing the other inactive layouts, since they were not meant to be
similar in size in the first place.

This patch creates a function that will be used to differentiate these
two different use of layouts.

Don't blacklist yuv converters, since those are needed for DVB subtitle display (thanks a bunch, Martin)

Don't blacklist the adjust filter, since it is supported by MobileVLCKit now

Don't build libmad, since libav can decode mp3 just fine

add mooar debug for ARM builds

Use 'input_item_GetTitleFbName', since this is actually the function used
to display title in the qt4 playlist.

Instead of hardcoding what we think the name of the current item is, make it
configurable via the --input-title-format parameter.

This change makes skins2 more consistent with qt4 that already uses this
means to set the title of the main window.

Default display will now be "artist + title" instead of just "title".
Users who would still prefer the previous behaviour can get it with
--input-title-format '$t'

This fixes a request described at http://forum.videolan.org/viewtopic.php?f=15&t=108976

Error messages were reused from time when there was no uncommitted
switch support. Now we have support for this feature, and we can
supply better error messages, because we know in more details what
has happened at times when error occured.
Signed-off-by: Rémi Denis-Courmont <remi@remlab.net>

These sources have some data appended after the CC units.
Example: 0x91 0xe0 0x65 0x6e 0x67 0x7e 0x3f 0xff
                     e    n    g
Probably a language code.