Mir

lp:~raof/mir/buildsystems-are-the-worst

Created by Chris Halse Rogers and last modified
Get this branch:
bzr branch lp:~raof/mir/buildsystems-are-the-worst
Only Chris Halse Rogers can upload to this branch. If you are Chris Halse Rogers please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Chris Halse Rogers
Project:
Mir
Status:
Development

Recent revisions

1860. By Chris Halse Rogers

Merge trunk

1859. By Chris Halse Rogers

Don't let CMake play with rpath, it cuts itself.

So, the awesome thing about rpath is that it PRECEEDS all the other paths.
If, just for the sake of argument, your cross compiles set an rpath-link to
your partial chroot you'd find that you're surprisingly linking against the
version of libmirclient.so.8 found in there.

Fixes the multiple inclusion of protobuf singletons caused when the system
Mir stuff is linking against one version of libmircommon and we're building
a new version.

1858. By Chris Halse Rogers

Check that the MirConnection is valid in BasicClientServerFixture.

1857. By Chris Halse Rogers

Abort test when InProcessServer startup fails.

ASSERT_TRUE does not actually abort the test unless called directly within
the main test body or from a function called within ASSERT_NO_FATAL_FAILURE()
within the main test body.

Throw an exception instead, which will terminate the test unless deliberately
caught.

1856. By Alan Griffiths

cmake: Fix dependencies on non-existent (renamed) protobuf targets

1855. By Alan Griffiths

tools: The tools/install_on_android.sh needs updating with current binaries

1854. By Daniel van Vugt

Remove reference to non-existent empty variable ${PROTO_HDRS}

1853. By Daniel van Vugt

DemoRenderer: Don't try to create a texture of width zero. libGL might crash
and definitely won't produce anything useful. This simple regression was
caused by accidentally changing float corner_radius = 0.5f into an int in
revision 1845. (LP: #1358210)

1852. By Alexandros Frantzis

client: Fix SIGTERM dispatch in our default lifecycle event handler, which
was resulting in clients looping infinitely in exception handlers
(LP: #1353867)

Our default lifecycle event handler used to call raise() to send a TERM
signal to the app when a connection break was detected. However, in a
multi-threaded program raise() sends the signal to the current thread only.
If the signal is blocked in that thread, then the signal is lost.

Depending on thread in which we detected that the connection was lost, the
TERM signal would be dispatched (e.g. in the context of a driver callback
asking for the next buffer) or not (e.g. in the context of our main RPC
threads which block all signals). This MP fixes the issue by explicitly
sending the signal to the process instead of the current thread. This ensures
that it will be dispatched to some thread that doesn't block it.

1851. By Daniel van Vugt

Draft changelog for the big things coming in 0.7
.

Approved by PS Jenkins bot, Cemil Azizoglu.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp:mir/ubuntu
This branch contains Public information 
Everyone can see this information.