View Single Post
Old 09-03-2024, 09:29 PM   #54
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,734
Karma: 206739468
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
I don't add anything like that when building Qt or Sigil. Not to say something like that is not introduced somewhere--just that I'm not knowingly doing it.

One other thing I never thought of is that those building their own Sigil are very likely using my Qt6.7.2 built for GitHub CI. It's not built with link time optimizations (so as to be compatible with any version of VS2022 installed on Github's runner images [or any versions users may have installed]). Whereas I'm using a version built with link time optimizations for releases and for my own Sigil development. I've not made that Qt build available publicly.

When Qt is built with link time code generation enabled, then Sigil MUST be built with the exact same VS toolchain version. Perhaps that's the difference.

I guess I can check pretty easily by building Sigil with my CI version of Qt6.7.2

Last edited by DiapDealer; 09-03-2024 at 09:35 PM.
DiapDealer is offline   Reply With Quote