-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows: Enable EH Continuation Metadata #2159
Conversation
c8a164f
to
c26cf96
Compare
Previously I did not enable CFG/CET for RegressionTest Release x64. |
Oh and there is also MediaInfoShellExt.vcxproj which has CFG/CET enabled for Release but not EHCONT. |
c26cf96
to
beb580e
Compare
beb580e
to
d7a5758
Compare
Not needed, removed.
Needed, added. Thanks for double checking. |
@JeromeMartinez and I just discovered for ARM there is |
Looks like this option in Visual Studio is for enabling pointer authentication security mitigation on ARM. |
I'll let you manage that :-p. |
Might need to add ARM64EC or ARM64X build if you want to have native ARM MediaInfo.dll for the GUI on Windows 11 ARM64. |
After the first shot with DLL and CLI. |
If you make the CLI fully ARM64, need to build an ARM64 graph plugin for it right? |
And FFmpeg plugin. But really not the priority, ARM64 is already low usage, ARM64 plugins even lower. |
Or can just make the CLI ARM64EC so that it has native performance but can load x64 plugins. Microsoft and Qualcomm keeps pushing ARM64 so if they succeed, usage may increase significantly. |
Could work in this way? I thought it was ARM64EC = x64 --> ARM64EC, not ARM64EC --> x64. |
From what I read and understood, ARM64EC means can interface with x64 and ARM64EC any way we want but not with ARM64. There is also ARM64X which is ARM64 and ARM64EC in the same binary with size savings. This single binary can interface with x64, ARM64 and ARM64EC binaries. |
No description provided.