Date: prev next · Thread: first prev next last
2018 Archives by date, by thread · List index


On 21/11/2018 17:42, Stephan Bergmann wrote:
SUMMARY
=======

If nobody objects, we'd update the build baselines on master (towards LO 6.3) as follows (cf README.md):

* Windows: from Visual Studio 2017 to Visual Studio 2017 version 15.7

* macOS: from Xcode 8 to Xcode 9.3

* Linux GCC: from GCC 4.8.1 to GCC 7

* Linux Clang: from Clang to Clang 5.0.2

* Clang compiler plugins: from Clang 3.8 to Clang 5.0.2

* flex: from 2.5.35 to 2.6.0

* gperf: from 3.0.0 to 3.1

On Android, since <https://gerrit.libreoffice.org/plugins/gitiles/core/+/312eeeee42cb4a1e356943e17305555e41afc4ef%5E!/> "Switch Android armeabi-v7a to libc++/libc++abi/libunwind too", all architectures now build (with NDK 16) against a toolchain that appears to be recent enough, too: The used Clang is reported as

$ android-ndk-r16b/toolchains/llvm/prebuilt/linux-x86_64/bin/clang --version
Android clang version 5.0.300080  (based on LLVM 5.0.300080)
Target: x86_64-unknown-linux
Thread model: posix
InstalledDir: .../android-ndk-r16b/toolchains/llvm/prebuilt/linux-x86_64/bin

with an odd nonstandard version number of 5.0.300080, but which appears to be new enough; and the used libc++ is reported as

$ cat android-ndk-r16b/sources/cxx-stl/llvm-libc++/include/__libcpp_version 6000

i.e., libc++ 6. The CXXFLAGS_CXX11 in config_host.mk are detected as -std=gnu++1z, which is OK.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.