Open fire opened 3 years ago
Should we move the use of use_static_cpp=yes
only when production=yes
is passed? I feel it's a unnecessary hurdle for development builds (which you don't intend to redistribute), as mentioned numerous times in GitHub issues.
and it's required for that option in Ubuntu, fedora and Centos
libatomic is not required when using llvm/clang without static_cpp, so this patch works: https://github.com/LinuxUserGD/godot/commit/3b5ced37a7fad61d2263172f5ca39284fea48a78
libatomic is not required when using llvm/clang without static_cpp, so this patch works: LinuxUserGD/godot/commit/3b5ced37a7fad61d2263172f5ca39284fea48a78
That URL appears to be broken, likely because your fork repository is private.
That URL appears to be broken, likely because your fork repository is private.
Sorry, deleted the repository after merge. When using a linux system with llvm/clang toolchain without gcc dependencies, gcc needs to be manually installed to provide libatomic. So libatomic is probably not required for bootstrapped clang on Linux systems when linking with libc++: https://github.com/godotengine/godot/pull/71766/files
https://docs.godotengine.org/en/stable/development/compiling/compiling_for_x11.html
Before I forget.
libatomic has static versions and it's required for that option in Ubuntu, fedora and Centos