Print the logs only if their level is not under the threshold, which is
defined to INFO in release mode and DEBUG in debug mode.

CloseHandle() does not terminate the process. TerminateProcess() does.

All our logs should use APPLICATION category. The logs for other
categories are not printed by default under the "critical" level.

On our Windows machine, the mingw ld.exe does not support sanitizers.

Exclude them from the default debug build.

In release mode, use the default log priorities.

Because why not.

Characters like 'é' or 'î' are not resolved by getEvents(). For example,
getEvents("é") returns null.

However, it is possible to decompose them. For example,
getEvents("\u0301e") returns the events generating "é".

Thank you Philippe! ;)

The SDL clean up does not crash anymore on exit, probably since the
memory corruption caused by calling SDLNet_TCP_Close() too early has
been resolved.

Wait no more than 2 seconds for accepting the connection from the
device, since it blocks the event loop, preventing to react to SIGTERM
(Ctrl+C).

On startup, the client has to:
 1. listen on a port
 2. push and start the server to the device
 3. wait for the server to connect (accept)
 4. read device name and size
 5. initialize SDL
 6. initialize the window and renderer
 7. show the window

From the execution of the app_process command to start the server on the
device, to the execution of the java main method, it takes ~800ms. As a
consequence, step 3 also takes ~800ms on the client.

Once complete, the client initializes SDL, which takes ~500ms.

These two expensive actions are executed sequentially:

                     HOST              DEVICE
listen on port        |                  |
push/start the server |----------------->|| app_process loads the jar
accept the connection .   ^              ||
                      .   |              ||
                      .   | WASTE        ||
                      .   |  OF          ||
                      .   | TIME         ||
                      .   |              ||
                      .   |              ||
                      .   v              X execution of our java main
connection accepted   |<-----------------| connect to the host
init SDL             ||                  |
                     || ,----------------| send frames
                     || |,---------------|
                     || ||,--------------|
                     || |||,-------------|
                     || ||||,------------|
init window/renderer  | |||||,-----------|
display frames        |<++++++-----------|
(many frames skipped)

The rationale for step 3 occuring before step 5 is that initializing
SDL replaces the SIGTERM handler to receive the event in the event loop,
so pressing Ctrl+C during step 5 would not work (since it blocks the
event loop).

But this is not so important; let's parallelize the SDL initialization
with the app_process execution (we'll just add a timeout to the
connection):

                     HOST              DEVICE
listen on port        |                  |
push/start the server |----------------->||app_process loads the jar
init SDL             ||                  ||
                     ||                  ||
                     ||                  ||
                     ||                  ||
                     ||                  ||
                     ||                  ||
accept the connection .                  ||
                      .                  X execution of our java main
connection accepted   |<-----------------| connect to the host
init window/renderer  |                  |
display frames        |<-----------------| send frames
                      |<-----------------|

In addition, show the window only once the first frame is available to
avoid flickering (opening a black window for 100~200ms).

Note: the window and renderer are initialized after the connection is
accepted because they use the device information received from the
device.

Turning the screen on is semantically associated to control(): only
creating the EventController object should not turn the screen on.

Expose an initializer so that the caller does not have to guess what
fields must be initialized.

SDLNet_TCP_Close() not only closes, but also release the resources.

Therefore, we must not close the socket if another thread attempts to
read it.

For that purpose, move socket closing from server_stop() to
server_destroy().

"make build-debug" will build with ASAN and USAN enabled.

Replace screen_update() by a higher-level screen_update_frame() handling
the whole frame updating, so that scrcpy.c just call it without managing
implementation details.

Do not wait 100ms anymore to let the server print any exception: we
justly want to ignore them.

Moreover, there is no nanosleep() on Windows, so this solve another
problem.

On close, the socket is closed by the client, and the server process is
killed.

This leads to (expected) exceptions, that should not be printed.

When the video stream socket is closed and read_packey() returns -1,
av_read_frame() still returns 0.

To detect EOF, check the flag eof_reached in the AVIOContext.

This avoids garbage errors on closing.

Avoid to send the command twice, once on mouse down, once on mouse up.

On exit, the renderer will not consume frames anymore, so signal the
condition variable to wake up the decoder.

Expose frames_offer_decoded_frame() and frames_consume_rendered_frame()
so that callers are not exposed to frame swapping (between the decoding
and rendering frames) details.

The mutex was not unlocked on all code paths.

Move the code handling user input from scrcpy.c to a separate file,
screencontrol.c.

As soon as we accepted a connection, we can remove the "adb reverse"
tunnel.

Move the code to read the initial device info from scrcpy.c to a
separate file, device.c.

The file server.c already existed, but exposed a low-level API. Make it
higher-level, so that scrcpy.c does not handle server details directly.

The file scrcpy.c contains too many different things in addition to the
main logic, so move the screen code to a separate file, screen.c.

In practice, these headers are included only once, but it's a good
practice to always use include guards.

The struct decoder is defined in decoder.h.

For naming consistency, define the struct controller in controller.h.

Some functions in scrcpy.c are not used outside the file, so declare
them static.

Apply Genymobile checkstyle and gradle build files organization.

Use AXIS_HSCROLL (available since API 12) instead of AXIS_SCROLL (since
API 26).

In handleEvent(), connection.receiveControlEvent() may never return
null: either it returns a valid ControlEvent, either it throws an
Exception.

Therefore, there is no need to propagate a flag to indicate whether it
returned a valid ControlEvent.

Use one parse method per control event type.

The server is not a real Android application, it's just a jar with a
main method. Instrumented tests are meaningless in this context.

On some devices, we can reuse the same codec and display, but on some
others (e.g. Nexus 5X with Android 7.1.2), it crashes on codec.stop()
with an IllegalStateException.

Therefore, always recreate the codec and display, so that it works on
all devices.

If rotation changed, the dequeued output buffer was never released. Move
it to a finally block to avoid the leak.

Let some time to print any exception trace before killing it.

Log at debug level user requests to quit.

On --version, also print the dependencies version scrcpy has been
compiled against.