Prepare to run (select) tests during Emscripten build
commita3d758d528d3408fcccd7d3673439b5d68347e30
authorStephan Bergmann <stephan.bergmann@allotropia.de>
Tue, 30 Apr 2024 14:51:21 +0000 (30 16:51 +0200)
committerStephan Bergmann <stephan.bergmann@allotropia.de>
Thu, 2 May 2024 05:52:03 +0000 (2 07:52 +0200)
tree56c653af8f0c91f894c4a1c315c1567143b22a52
parent79b1a61303af8dc8716c03151b28bfce13162eb0
Prepare to run (select) tests during Emscripten build

...by e.g. executing generated Wasm code with node.  This requires check targets
to not be skipped unconditionally, unlike for other CROSS_COMPILING builds, so
introduce gb_CAN_EXECUTE_HOST_CODE to distinguish these cases.

Which revealed that some CppunitTest targets unconditionally used artefacts that
are covered by some ENABLE_WASM_STRIP_*, so made those uses conditional
accordingly (even though the resulting binaries might actually be dysfunctional,
lacking relevant parts; we'll fix that if and when we actually build and run
them).

Change-Id: I7144eeb908ede25358a3c8186198ac532de4d9f1
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166931
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <stephan.bergmann@allotropia.de>
drawinglayer/CppunitTest_drawinglayer_processors.mk
solenv/gbuild/extensions/post_SpeedUpTargets.mk
solenv/gbuild/gbuild.mk
solenv/gbuild/platform/EMSCRIPTEN_INTEL_GCC.mk
writerperfect/CppunitTest_writerperfect_epubexport.mk