On the latest CEF as of Sept 28, when running on Linux, our app cannot startup when linking against libcef.so. Our app is a very GPU intensive C++ Vulkan application. It seems bringing in libcef.so brings in it's own Vulkan loader and then when our application goes to init Vulkan it gets CEF's libvulkan.so.1. This runtime doesn't work for us because it seems to be unable to correctly enumerate the Installable Client Drivers (ICDs) and layers so we end up with missing extensions that might not matter to CEF but very much matter to an application trying to do real Vulkan work. (Shipping your own Vulkan runtime is frowned upon by the Vulkan community for this reason.
)If I delete libvulkan.so.1, our application can finally load again but then CefInitialize crashes.
Is there a proper flag or command line argument to pass to CefInitialize in our case where there is a guaranteed Vulkan runtime and we under no circumstances want CEFs?