是否有必要在顶层xmake.lua中添加add_cxflags("-fPIC")？

[wzhy]

你在什么场景下需要该功能？

在ARM64架构下的Linux系统中，编译出libtbox.a后在另外一个生成动态库的项目中使用，但未能成功：链接阶段报"relocation R_AARCH64_ADR_PREL_PG_HI21"错误。该项目改为生成可执行文件时（set_kind("shared") -->set_kind("binary") ），就没有此问题。

描述可能的解决方案

在tbox的顶层xmake.lua中add_cxflags("-fPIC")？
也许能解决上面碰到的问题，但尚未验证。

描述你认为的候选方案

无。

其他信息

无。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Title: Is it necessary to add add_cxflags("-fPIC") in the top-level xmake.lua?

In what scenario do you need this function?

In a Linux system under the ARM64 architecture, libtbox.a was compiled and used in another project to generate a dynamic library, but failed: the link phase reported a "relocation R_AARCH64_ADR_PREL_PG_HI21" error. When the project was changed to generate an executable file (set_kind("shared") -->set_kind("binary") ), there was no such problem.

Describe possible solutions

Add_cxflags("-fPIC") in the top-level xmake.lua of tbox?
It may be able to solve the problems encountered above, but it has not been verified yet.

Describe your alternatives

none.

Other information

none.

[waruqi]

不考虑，如果想在动态库里用 tbox，自己编译 tbox 时候，xmake f --cflags="-fPIC" 就行了。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Regardless, if you want to use tbox in a dynamic library, just xmake f --cflags="-fPIC" when compiling tbox yourself.

[wzhy]

建议在Readme或其他文档中提示一下这个fPIC问题，特别是对于非x86平台或有交叉编译的场合，现在搜索tbox编译相关的文档还都是只能编译成静态库……

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

It is recommended to mention this fPIC issue in the Readme or other documents, especially for non-x86 platforms or cross-compilation situations. Currently, searching for documents related to tbox compilation can only be compiled into a static library...