Use { ... } for grouping that does not need a sub-shell
...in case that makes ever so small a difference, esp. on Windows (where spawning processes is known to be expensinve; but note that at least Bash seems to not spawn a sub-shell anyway when what is enclosed in ( ... ) is just a simple single process, which is commonly the case for these cppunittester invocations) Change-Id: Ie9200270743754e02fbfdb2b17239e9873031dab Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102407 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
This commit is contained in:
parent
b3e4ba69b7
commit
51f4691e7f
1 changed files with 2 additions and 2 deletions
|
@ -123,7 +123,7 @@ else
|
|||
$(if $(gb_CppunitTest__interactive),, \
|
||||
$(if $(value gb_CppunitTest_postprocess), \
|
||||
rm -fr $@.core && mkdir $@.core && cd $@.core &&)) \
|
||||
( \
|
||||
{ \
|
||||
$(if $(gb_CppunitTest_localized),for l in $(WITH_LANG_LIST) ; do LO_TEST_LOCALE="$$l" ) \
|
||||
$(if $(gb_CppunitTest_PREGDBTRACE),$(gb_CppunitTest_PREGDBTRACE) &&) \
|
||||
$(if $(gb_CppunitTest__vcl_no_svp), \
|
||||
|
@ -141,7 +141,7 @@ else
|
|||
$(if $(gb_CppunitTest_POSTGDBTRACE), \
|
||||
; RET=$$? && $(gb_CppunitTest_POSTGDBTRACE) && (exit $$RET)) \
|
||||
$(if $(gb_CppunitTest_localized),|| exit $$?; done) \
|
||||
) \
|
||||
; } \
|
||||
$(if $(gb_CppunitTest__interactive),, \
|
||||
> $@.log 2>&1 \
|
||||
|| ($(if $(value gb_CppunitTest_postprocess), \
|
||||
|
|
Loading…
Reference in a new issue