I'm writing some C++ code which I might eventually like to release under an Apache v2.0 license.
I'm looking to build the application linking to some of the LGPL v2.1-licensed shared libraries from Gnu GPG.
I shall not be statically linking with Gnu GPG libraries.
I shall NOT be including any Gnu GPG shared libraries or any other part of Gnu GPG when distributing my application.
Users will either already have them installed or will have to install them separately. In the absence of the Gnu GPG shared libraries, my application will continue to run without GPG functionality.
The LGPL v2.1 license wording appears to allow dynamically loaded shared libraries to be used in this way by applications which are licensed with licenses other than LGPL.
The question I have is this:
Is it permissible for me to distribute my application under the Apache 2.0 License if it dynamically links with LGPL v2.1 shared libraries as described above, and those LGPL shared libraries are not included in my distribution?
Otherwise, are there compatibility problems arising from the Apache license side ?