android ndk开发中的gnustl和stlport有什么区别? [英] What' s the difference between gnustl and stlport in android ndk development?

问题描述

我想知道它们的性能/稳定性是否彼此不同，并简要说明其许可证.欢迎您体验现实世界.

I want to know if their performance/stability differ from each other and their licenses explained in short. Real world experiences are welcomed.

推荐答案

截至昨天(NDK r9d)，gnustl仍然更加全面，例如支持< thread>，< future>和其他一些C ++ 11功能.甚至这些都取决于工具链:您无法使用默认的ARM gcc 4.6启用它们.

As of yesterday (NDK r9d), gnustl was still more comprehensive, e.g. support for <thread>, <future>, and some other C++11 features. Even these depend on the toolchain: you could not use the default ARM gcc 4.6 to have them enabled.

OTOH，与AOSP的其余部分一样，stlport许可证是免费的，而对于gnustl的GPL v3链接异常并不容易理解.请参见 https://groups.google.com/d/topic/android-ndk/OWl_orR0DRQ 进行一些较早的讨论.

OTOH, stlport license is no-nonsense free, like the rest of AOSP, while the linking exception to GPL v3 for gnustl is not easy to understand. See https://groups.google.com/d/topic/android-ndk/OWl_orR0DRQ for some older discussion.

如果查看NDK发行说明，您会发现就固定的错误而言，这两个STL实现或多或少地相提并论.

If you look at the NDK release notes, you will find that in terms of fixed bugs these two STL implementations were more or less on par.

我很高兴看到性能基准，但就我个人而言，我从未遇到过STL实现变化解决了真正瓶颈的情况.

I would be glad to see performance benchmarks, but personally I have never encountered a situation where STL implementation variation resolved a real bottleneck.

这篇关于android ndk开发中的gnustl和stlport有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！