View Single Post
Old 09-06-2025, 11:58 AM   #64
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,737
Karma: 206739468
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
I just can't manage the single package any more. The resulting package is too huge and can't easily be uploaded for CI, or be easily moved to other machines. It actually results in more unnecessary modules, plugins and cruft being linked into the Windows Sigil bundle too. Building only the modules that are necessary for Sigil is the only way I can keep my Qt6 environment (not to mention the Sigil installer bundles) small enough to be useful.

I will try an all-in-one build sometime just to rule out the possibility that my methods are causing the slowdown. I just don't see how it could be, though, since the QtWebEngine build alone takes hours and hours. And it uses ninja, which automatically makes use of parallel processing.

Last edited by DiapDealer; 09-06-2025 at 12:08 PM.
DiapDealer is offline   Reply With Quote