Replies: 1 comment
-
|
I briefly looked into the M138 version, and as you mentioned, it introduces significant architectural changes. Unfortunately, I don’t have time to work on adapting to the new version at the moment. That said, I’m hoping to revisit this later in the year and plan for proper integration when my schedule allows. Thanks for your understanding. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
CEF v138 Integration Issue: "Parse process unknown, exit" Error
Environment
Issue Description
I attempted to integrate CEF v138 with QCefView, but the application immediately terminates with the error message:
Background
I understand that CEF v138 introduced significant architectural changes, specifically:
Questions
Compatibility Status: Is QCefView currently compatible with CEF v138 and later versions that use Chrome runtime exclusively?
Migration Plan: Are there any plans to update QCefView to support the new Chrome runtime-only architecture?
Workaround: Is there any configuration or code modification that could make QCefView work with CEF v138?
Recommended CEF Version: What is the latest CEF version that is known to work reliably with the current QCefView implementation?
Configuration Used
thirdparty/CMakeLists.txt
Thank you for your time and for maintaining this excellent library!
Beta Was this translation helpful? Give feedback.
All reactions