Original issue 109 created by christophe.cornu on 2014-08-15T18:35:40.000Z:
Congrats on the work for revision 99 with the adoption of CEF 3.1916.1749 and the Mac fix for visibility. For the first time we can have multiple tabs working on the Mac :-) I did notice a regression affecting those that launch their app through the java command line. Details below.
What steps will reproduce the problem?
1. Get and build latest JCEF r99 on Mac
2. Double click on jcef_app.app. All works fine.
3. Start a Java program that uses jcef, from the command line (using e.g. /Library/Java/JavaVirtualMachines/jdk1.7.0_55.jdk/Contents/Home/bin/java)
What is the expected output? What do you see instead?
When starting the program from the command line with the java executable, Java_org_cef_CefApp_N_1Initialize fails with the following msg.
[0815/140948:FATAL:content_main_runner.cc(751)] Check failed: base::i18n::InitializeICU().
A bad workaround is to copy icudtl.dat from jcef_app.app/Contents/Frameworks/Resources/ to /Library/Java/JavaVirtualMachines/jdk1.7.0_55.jdk/Contents/Home/bin/java (or wherever your java executable is installed).
What do you recommend to have util_mac::CefInitializeOnMainThread find icudtl.dat in the right location instead of getting it from the main executable's path? pathToJavaDLL points to jcef_app.app/Contents/Java, we can build the full path pointing to jcef_app.app/Contents/Frameworks/Resources/. How can we tell CEF to use that location?
These 2 links are interesting.
This was not a pb with former revisions (r90) when icudtl.dll was loaded as a dll directly.