Discussion:
Change MSVC compatibility for clang-cl
(too old to reply)
Julius Bullinger
2018-11-29 08:50:25 UTC
Permalink
Hi,

is there a way to change the MSVC compatibility/ABI
(``-fms-compatibility``, see
https://clang.llvm.org/docs/MSVCCompatibility.html) for detected
clang-compilers in Creator?

clang-cl is autodetected as "MSVC2017" compatible and vcvarsall.bat from
VS2017 is called. But we change the compatibilty in our .pro file to
MSVC2013, so the wrong system headers are included.

For manually added clang (without -cl), the ABI can be set, but that is
not possible for clang-cl.

If not, should I file a feature request in JIRA?

Thanks and best regards,
Julius
Ivan Donchevskii
2018-11-29 09:13:53 UTC
Permalink
Hi,


Should be possible to do. "file a feature request in JIRA" - yes, please. You can assign it to me, I think I touched this part the last time.

Also please specify what do you mean by "change the compatibilty in our .pro file to MSVC2013".


Kind regards,

Ivan

________________________________
From: Qt-creator <qt-creator-***@lists.qt-project.org> on behalf of Julius Bullinger <***@mvtec.com>
Sent: Thursday, November 29, 2018 9:50:25 AM
To: qt-***@qt-project.org
Subject: [Qt-creator] Change MSVC compatibility for clang-cl

Hi,

is there a way to change the MSVC compatibility/ABI
(``-fms-compatibility``, see
https://clang.llvm.org/docs/MSVCCompatibility.html) for detected
clang-compilers in Creator?

clang-cl is autodetected as "MSVC2017" compatible and vcvarsall.bat from
VS2017 is called. But we change the compatibilty in our .pro file to
MSVC2013, so the wrong system headers are included.

For manually added clang (without -cl), the ABI can be set, but that is
not possible for clang-cl.

If not, should I file a feature request in JIRA?

Thanks and best regards,
Julius
Julius Bullinger
2018-11-29 09:47:57 UTC
Permalink
------------------------------------------------------------------------
*Sent:* Thursday, November 29, 2018 9:50:25 AM
*Subject:* [Qt-creator] Change MSVC compatibility for clang-cl
Post by Julius Bullinger
Hi,
is there a way to change the MSVC compatibility/ABI
(``-fms-compatibility``, see
https://clang.llvm.org/docs/MSVCCompatibility.html) for detected
clang-compilers in Creator?
clang-cl is autodetected as "MSVC2017" compatible and vcvarsall.bat from
VS2017 is called. But we change the compatibilty in our .pro file to
MSVC2013, so the wrong system headers are included.
For manually added clang (without -cl), the ABI can be set, but that is
not possible for clang-cl.
If not, should I file a feature request in JIRA?
Thanks and best regards,
Julius
Should be possible to do. "file a feature request in JIRA" - yes,
please. You can assign it to me, I think I touched this part the
last time.
Also please specify what do you mean by "change the compatibilty in
our .pro file to MSVC2013".
Kind regards,
Ivan
I filed QTCREATORBUG-21604. I cannot change the Assignee, so please feel
free to assign yourself.

Thank you!

Marco Bubke
2018-11-29 09:35:29 UTC
Permalink
HI Julius


It's always better to use JIRA. We maybe should add a tool chain for clang-cl but I am not an expert in this area. Lets discuss that in JIRA so it got not lost.


Best Marco

________________________________
From: Qt-creator <qt-creator-***@lists.qt-project.org> on behalf of Julius Bullinger <***@mvtec.com>
Sent: Thursday, November 29, 2018 9:50:25 AM
To: qt-***@qt-project.org
Subject: [Qt-creator] Change MSVC compatibility for clang-cl

Hi,

is there a way to change the MSVC compatibility/ABI
(``-fms-compatibility``, see
https://clang.llvm.org/docs/MSVCCompatibility.html) for detected
clang-compilers in Creator?

clang-cl is autodetected as "MSVC2017" compatible and vcvarsall.bat from
VS2017 is called. But we change the compatibilty in our .pro file to
MSVC2013, so the wrong system headers are included.

For manually added clang (without -cl), the ABI can be set, but that is
not possible for clang-cl.

If not, should I file a feature request in JIRA?

Thanks and best regards,
Julius
Loading...