本文探讨了使用arm-linux-gnueabihf-gcc和arm-linux-androideabi-gcc在Android上进行静态编译时遇到的问题，包括getpwnam函数缺失、静态链接库的大小和复杂性、以及Android对某些库的支持情况。文章通过实例分享了编译nginx和openssl的经验，指出静态编译时需要针对Android环境修改代码、配置编译选项，以及解决静态链接curl时的限制。
想在手机上做一些工作，但不是很想用android 的不开源的东西。所以编译工具arm-linux-gnueabihf-gcc，这个在用static编译选项时对多数程序，除编出来的有点大外都是可用的。但对getpwnam等.
Is linking statically (or: bundling all the libraries you need with your software) a solution? Even if it works technically, the associated costs might be to high. So unfortunately, the answer is probably no either.
-
Security: you shift the responsibility to update the libraries from the user of your software to yourself.
-
Size and complexity: just for fun try to build a statically linked GUI program.
-
Interoperability: if your software is a "plugin" of any kind, you depend on the software which calls you.
-
Library design: if you link your program statically to GNU libc and use name services (
getpwnam()etc.), you end up linked dynamically against libc's NSS (name service switch). -
Library design: the library you link your program s
最低0.47元/天 解锁文章
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
