I don't know what's the best way to handle this - many packages in the archive don't know about mir, and SDL just pulled it in - and SDL isn't telling the build process where MIR is located. There isn't enough time to find them all and fix it before trusty is released.
Since we're so close to an LTS release, should MIR support be dropped from SDL2?
ok, so it looks like libsdl2 has to update/use pkgconfig and pass those headers.
This is related to: /bugs.launchpad .net/mir/ +bug/1161064 /bugs.launchpad .net/mir/ +bug/1161240
https:/
https:/
I don't know what's the best way to handle this - many packages in the archive don't know about mir, and SDL just pulled it in - and SDL isn't telling the build process where MIR is located. There isn't enough time to find them all and fix it before trusty is released.
Since we're so close to an LTS release, should MIR support be dropped from SDL2?