termux-packages/packages/libc++/build.sh

TERMUX_PKG_HOMEPAGE=https://libcxx.llvm.org/
TERMUX_PKG_DESCRIPTION="C++ Standard Library"
TERMUX_PKG_LICENSE="NCSA"
TERMUX_PKG_MAINTAINER="@termux"
TERMUX_PKG_VERSION=$TERMUX_NDK_VERSION
TERMUX_PKG_REVISION=1
TERMUX_PKG_SKIP_SRC_EXTRACT=true
TERMUX_PKG_ESSENTIAL=true

termux_step_post_make_install() {
	cp "$TERMUX_STANDALONE_TOOLCHAIN/sysroot/usr/lib/${TERMUX_HOST_PLATFORM}/libc++_shared.so" $TERMUX_PREFIX/lib
}
Transition from gnustl to libc++ This will make things as std::to_string() and other C++ features work with a modern and supported C++ library. We package up libc++_shared.so and bump the revision of every C++ using package to make it rebuild against it. Users who have built C++ using libraries or programs will probably need to rebuild them if they are linked against Termux-supplied libraries, as user code was previously linked against gnustl while the system libraries are now using libc++, and it's not a good idea to mix C++ standard libraries in a program. 2017-07-14 00:23:37 +02:00			`TERMUX_PKG_HOMEPAGE=https://libcxx.llvm.org/`
			`TERMUX_PKG_DESCRIPTION="C++ Standard Library"`
fix licenses where possible Some packages have license set to "custom" and this should be fixed. 2019-01-21 15:00:12 +01:00			`TERMUX_PKG_LICENSE="NCSA"`
explicitly set maintainer for each package In issue https://github.com/termux/termux-packages/issues/6160 I have found that community repo "its-pointless.github.io" specifies us as maintainer for its packages. This is NOT TRUE and potentially misleads people using these packages. Now TERMUX_PKG_MAINTAINER will contain a default value which is neutral and not specify maintainer. So all packages now have to override it to the correct value. [skip ci] %ci:no-build 2020-12-20 14:16:34 +01:00			`TERMUX_PKG_MAINTAINER="@termux"`
Transition from gnustl to libc++ This will make things as std::to_string() and other C++ features work with a modern and supported C++ library. We package up libc++_shared.so and bump the revision of every C++ using package to make it rebuild against it. Users who have built C++ using libraries or programs will probably need to rebuild them if they are linked against Termux-supplied libraries, as user code was previously linked against gnustl while the system libraries are now using libc++, and it's not a good idea to mix C++ standard libraries in a program. 2017-07-14 00:23:37 +02:00			`TERMUX_PKG_VERSION=$TERMUX_NDK_VERSION`
libc++: bump to build r21d 2020-07-10 22:02:55 +02:00			`TERMUX_PKG_REVISION=1`
add new linter script & fix packages where needed Linter will check packages submitted for CI build. If error was found, build will not be allowed. To ensure that all build.sh scripts are consistent and have at least minimal allowed quality, linter is permanently enabled for all branches and pull requests. 2019-08-14 13:27:16 +02:00			`TERMUX_PKG_SKIP_SRC_EXTRACT=true`
packages: standardize values of several control variables for build.sh Variables TERMUX_PKG_PLATFORM_INDEPENDENT TERMUX_DEBUG TERMUX_PKG_HAS_DEBUG TERMUX_PKG_ESSENTIAL TERMUX_SUBPKG_ESSENTIAL TERMUX_PKG_NO_STATICSPLIT TERMUX_PKG_BUILD_IN_SRC TERMUX_PKG_FORCE_CMAKE TERMUX_PKG_HOSTBUILD should not accept arbitrary values for marking them "enabled". Instead they should accept boolean values which makes them easier to handle and also makes their meaning clear. build-package.sh should make decision based on variable's value but not on whether it is set or empty. %ci:no-build 2019-08-12 17:28:41 +02:00			`TERMUX_PKG_ESSENTIAL=true`
Transition from gnustl to libc++ This will make things as std::to_string() and other C++ features work with a modern and supported C++ library. We package up libc++_shared.so and bump the revision of every C++ using package to make it rebuild against it. Users who have built C++ using libraries or programs will probably need to rebuild them if they are linked against Termux-supplied libraries, as user code was previously linked against gnustl while the system libraries are now using libc++, and it's not a good idea to mix C++ standard libraries in a program. 2017-07-14 00:23:37 +02:00
Simplify libc++ setup As clang++ in the NDK defaults to libc++ since r17, we no longer need to fake a libstdc++.so at build time (and omit it from the libc++ package we ship). 2019-03-11 09:33:12 +01:00			`termux_step_post_make_install() {`
			`cp "$TERMUX_STANDALONE_TOOLCHAIN/sysroot/usr/lib/${TERMUX_HOST_PLATFORM}/libc++_shared.so" $TERMUX_PREFIX/lib`
Transition from gnustl to libc++ This will make things as std::to_string() and other C++ features work with a modern and supported C++ library. We package up libc++_shared.so and bump the revision of every C++ using package to make it rebuild against it. Users who have built C++ using libraries or programs will probably need to rebuild them if they are linked against Termux-supplied libraries, as user code was previously linked against gnustl while the system libraries are now using libc++, and it's not a good idea to mix C++ standard libraries in a program. 2017-07-14 00:23:37 +02:00			`}`