Closed cjee21 closed 1 week ago
I prefer to keep a coherence so to change that everywhere.
I can change for others as well but it will be untested.
About
$$PWD
, what is the issue without it? It seems to work well without it.
Without this I get many linker errors of things not found during the linking stage.
Beside Qt project, if you don't mind, please check, enable if needed, test and send another PR for VS2022 as well as VS2019 (we didn't yet upgraded VS on our build farm), for all repositories. Nothing mandatory if you don't want to do that, just a wish.
I'll see what I can do when I'm free.
As we are there, you may be curious about CET, and try CET option. As we don't have a CPU supporting CET, we didn't try but it would be great if it is doable.
My CPU seems supported. I'll check it out.
There is also Spectre mitigations but I'm not sure if relevant for MediaInfo. This one is known to affect performance. This one is enabled in my Windows 11 context menu PoC.
I can change for others as well but it will be untested.
Similar update so I take the risk :).
Without this I get many linker errors of things not found during the linking stage.
Weird, Fedora uses it and seems fine, @g-maxime can you check that mediainfo-qt
package still compiles on Fedora?
There is also Spectre mitigations but I'm not sure if relevant for MediaInfo. This one is known to affect performance.
IMO the "cost" of this option is higher than the benefit we may have with it, so I wouldn't add it until they find a less impacting mitigation.
Weird, Fedora uses it and seems fine, @g-maxime can you check that
mediainfo-qt
package still compiles on Fedora?
Only affects Windows MSVC as far as I know. It built fine on Ubuntu without any changes.
Only affects Windows MSVC as far as I know. It built fine on Ubuntu without any changes.
Oops, true, so @g-maxime no need to test.
It works! :D Tested on AMD CPU.
Beside Qt project, if you don't mind, please check, enable if needed, test and send another PR for VS2022 as well as VS2019 (we didn't yet upgraded VS on our build farm), for all repositories. Nothing mandatory if you don't want to do that, just a wish.
PRs created for MediaInfoLib, ZenLib and zlib.
Also for MediaInfo CLI. There are probably other MSVC Projects which I did not touch because I do not know their purpose.
FYI The HTML view in Qt version already has proper dark mode support on Windows.
EDIT: This is before the HTML patch for MediaInfoLib. It has extra cells on the first row. Can't find why it displays so many borders.
PRs created for MediaInfoLib, ZenLib and zlib.
Also for MediaInfo CLI. There are probably other MSVC Projects which I did not touch because I do not know their purpose.
@JeromeMartinez Confirmed that most recent dev build has CFG and CET enabled for MediaInfo DLLs and CLI
A collection of improvements made while I was exploring the Qt version of MediaInfo.
/guard:cf
enabled inProject | Properties | Configuration Properties | C/C++ | Code Generation
of their respective Visual Studio Projects.QIcon::fromTheme(QIcon::ThemeIcon::WindowClose)
when built with Qt > 6.7mainwindow.cpp
.mainwindow.cpp
.Tested with Qt 6.7.2 and MSVC2022.
Windows 11 screenshots: Process Explorer showing 64-bit Qt version with DEP, ASLR, CFG and Per-monitor DPI Awareness enabled
Ubuntu screenshots:
Previous screenshots for comparison: https://github.com/MediaArea/MediaInfo/pull/857#issuecomment-2152643509 https://github.com/MediaArea/MediaInfo/pull/857#issuecomment-2176644649