Re: [Interest] MSVC not-the-latest: are you using it? why?

Hi Thiago, The team I'm working with have been keeping up with the latest VS version - mainly for the security fixes and new C++11/17/20 features available in Qt 5.15.  But VS2022 introduced changes to the enum handling last year, which has made Intellisense useless for them - especially clas

Re: [Interest] MSVC not-the-latest: are you using it? why?

On Monday, 23 January 2023 09:19:07 PST Scott Bloom wrote: > One of the limiting factors in general, is we would prefer NOT to have 2 > compilers with very different c++ support. There have a been a number of " > C++11/14/17 etc" that have been partially implemented on one, and not on > the other.

Re: [Interest] MSVC not-the-latest: are you using it? why?

-Original Message- From: Interest On Behalf Of Thiago Macieira Sent: Sunday, January 22, 2023 9:32 AM To: interest@qt-project.org Subject: Re: [Interest] MSVC not-the-latest: are you using it? why? On Sunday, 22 January 2023 08:33:43 PST coroberti wrote: > On some update of MSVC-2017 to t

Re: [Interest] What is the right way of creating a static lib that has qml resources with cmake?

Indeed, /wholearchive exists on windows and can be used with the referenced cmake version, but unfortunately: - ensuring certain symbols are not discarded - others are (-gc-sections), - it works reliably - for all platforms that qt supports is more involved. See QTBUG-97816 , the comments ther

Re: [Interest] What is the right way of creating a static lib that has qml resources with cmake?

>> Yes, there is. There's -Wl,--whole-archive for the Unix linkers. This should >> solve the problem for everyone except MSVC users. > That option is not very attractive because: > a, as you state yourself, it doesn't work on MSVC. MSVC also has a /wholearchive