$MIR_CLIENT_PLATFORM_PATH and the executable_path() hack looks fragile.
We could write DefaultConnectionConfiguration::the_client_platform_factory() to use dladdr() to locate libmirclient.so and locate the client-modules directory relative to that? (which should be the same in tree and installed.)
$MIR_CLIENT_ PLATFORM_ PATH and the executable_path() hack looks fragile.
We could write DefaultConnecti onConfiguration ::the_client_ platform_ factory( ) to use dladdr() to locate libmirclient.so and locate the client-modules directory relative to that? (which should be the same in tree and installed.)