Since we're building a2play along with the library, it's normally going to be built before the library is installed. This has the undesired side effect that, when building a dynamic library, the a2play executable will actually try to load the lib in the build directory, instead of the installed one.
It will still find the system one if the build tree is cleaned, so it's probably not a showstopper, but this might call for some further investigation at least.
Since we're building a2play along with the library, it's normally going to be built before the library is installed. This has the undesired side effect that, when building a dynamic library, the a2play executable will actually try to load the lib in the build directory, instead of the installed one.
It will still find the system one if the build tree is cleaned, so it's probably not a showstopper, but this might call for some further investigation at least.