From cf0ed4fb4a610a61332a418f12b547648c3a0130 Mon Sep 17 00:00:00 2001 From: Stephan Bergmann Date: Wed, 14 Oct 2020 17:48:36 +0200 Subject: More fixes of uses of now-explicit OUString ctor taking raw sal_Unicode pointer ...in Windows-only code, after c927aab29ebfff1ce3ac0b2f27ae343025a9890c "Make the OUString ctors taking raw sal_Unicode pointer/non-const array explicit". Interestingly, these occurrences were accepted by MSVC and only cause errors with clang-cl, so happened to go unnoticed until now. Change-Id: I33e7653e28a21541ef793b4b0750abb6037752db Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104314 Tested-by: Jenkins Reviewed-by: Stephan Bergmann --- xmlsecurity/source/xmlsec/mscrypt/securityenvironment_mscryptimpl.cxx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'xmlsecurity') diff --git a/xmlsecurity/source/xmlsec/mscrypt/securityenvironment_mscryptimpl.cxx b/xmlsecurity/source/xmlsec/mscrypt/securityenvironment_mscryptimpl.cxx index 01b27fb9756f..c62c96d77328 100644 --- a/xmlsecurity/source/xmlsec/mscrypt/securityenvironment_mscryptimpl.cxx +++ b/xmlsecurity/source/xmlsec/mscrypt/securityenvironment_mscryptimpl.cxx @@ -249,7 +249,7 @@ static OUString get_system_name(const void *pvSystemStore, { ppwszSystemName = static_cast(pvSystemStore); } - return o3tl::toU(ppwszSystemName); + return OUString(o3tl::toU(ppwszSystemName)); } extern "C" { -- cgit