office-gobmx/smoketest
Stephan Bergmann b1141fa610 Cut down on -pthread/-lpthread proliferation
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>
2019-04-25 21:27:43 +02:00
..
com/sun/star/comp/smoketest
data
org/libreoffice/smoketest
CppunitTest_smoketest.mk
Executable_libtest.mk Cut down on -pthread/-lpthread proliferation 2019-04-25 21:27:43 +02:00
Extension_TestExtension.mk
Jar_smoketest.mk
Jar_TestExtension.mk
Library_smoketest.mk
libtest.cxx tdf#120703 PVS: V560 A part of conditional expression is always true/false 2018-11-25 16:52:30 +01:00
Makefile
Module_smoketest.mk
README
smoketest.cxx loplugin:constfields in smoketest..sot 2018-10-09 08:10:24 +02:00
smoketest_too.cxx
Zip_smoketestdoc.mk

Smoke test for each component of LibreOffice.

* smoketest:

	The main smoketest.cxx is launched connects via binary UNO
over a socket to a remote LibreOffice instance. This loads a document
which is zipped at build time into the workdir/ from the data/
directory. This in turn contains a set of macros in
data/Basic/Standard.

	Smoketest.cxx does a remote the StartTestWithDefaultOptions
macro and waits for a dispatchFinished from the macro's execution. To
debug this best load workdir/Zip/smoketestdoc.sxw - and hit 'start
smoketest' - this will launch a number of components and build a
suitable report in the form of a table.

	The StarBasic smoketests also log their output, this ends up
in instdir/user/temp/smoketest.log.