b1141fa610
Building against libstdc++ effectively always requires -pthread anyway (as various standard C++ headers require it, see the comment added to solenv/gbuild/platform/unxgcc.mk), so many explicit uses of -pthread/-lpthread can be removed. Doing a (partial) test build on Linux with Clang -stdlib=libc++ suggests that libc++ indeed doesn't need -pthread as libstdc++ does. The remaining uses of -pthread/-lpthread are mostly in configure.ac for the various BSDs (which somebody else might want to clean up now), and related to external projects. I tried to be careful to remove -pthread/-lpthread from makefiles only when C++ object files are involved (so -pthread will now be included on the link command line by default). Change-Id: I936e082839cb9a434bd273ce5a1f187a4245dfa1 Reviewed-on: https://gerrit.libreoffice.org/71291 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com> |
||
---|---|---|
.. | ||
inc | ||
qa | ||
source | ||
workben | ||
astyle.options | ||
CustomTarget_generated.mk | ||
Executable_mar.mk | ||
Executable_mbsdiff.mk | ||
Executable_test_updater_dialog.mk | ||
Executable_update_service.mk | ||
Executable_updater.mk | ||
Makefile | ||
Module_onlineupdate.mk | ||
README | ||
StaticLibrary_libmar.mk | ||
StaticLibrary_libmarverify.mk | ||
StaticLibrary_updatehelper.mk | ||
WinResTarget_updater.mk |
Online update implementation based on Mozilla's MAR format + update mechanism Parts of this code are copied from the mozilla repository, and adapted to LibreOffice needs: firefox/modules/libmar -> onlineupdate/source/libmar firefox/toolkit/mozapps/update -> onlineupdate/source/update The source/service directory contains the code for the silent windows updater that avoids the repeated administrator check for an update. == NOTE == The updater executable should not depend on any other dynamic library in the LibreOffice installation as we would need to copy that one also to a temporary directory during update. We can't update any library or executable that is currently in use. For the updater executable we solve this problem by copying the updater before using it to a temporary directory. On Windows we use the system to provide us with a crypto library whereas on Linux we use NSS. == Update procedure == The updater executable is run two times. In a first run, the current installation is copied to a "update" directory and the update is applied in this "update" directory. During the next run, a replacement request is executed. The replacement request removes the old installation directory and replaces it with the content of the "update" directory. === User profile in the installation directory === The archive based installations have the user profile by default inside of the installation directory. During the update process this causes some problems that need special handling in the updater. * The "update" directory is inside of the user profile resulting in recursive copying. * During the replacement request the updater log is in the user profile, which changes location from the actual location to a backup location.