On Tuesday, January 5, 2016 at 10:27:06 AM UTC-5, [email protected] wrote: > > I was just talking to some Qt people about the stlport issues I'm having > they told me I need to link against gnu-shared. Which is completely doable > in Crypto++ for android. But I mentioned the GPL issue and they seemed to > not think it was an issue, so I goodled. I found: > https://gcc.gnu.org/onlinedocs/libstdc++/faq.html#faq.license.what > > So it seems there there is a special exception for this library for use in > proprietary apps. I don't know if that changes anything, but I thought I'd > mention it, because the docs say > > *The second optional argument is a STL library. The default is STLport as > a shared library due to GNU licensing requirements. STL libraries can be > one of:* > > - *stlport (shared)* > - *stlport-static* > - *stlport-shared* > - *gnu (shared)* > - *gnu-static* > - *gnu-shared* > > Which raises the question, are we choosing the wrong default? >
Well, I can't speak for others, but this is the kind of thing I would prefer to avoid. In my mind's eye, they are useless problems created by lawyers. Instead of doing real work, we are now spending time on this. I'm probably a bit jaded, but I feel like these debates have a life of their own, and they get endlessly debated. With that said, I'll be happy to change things to whatever the group wants. Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
