CEF Version

[Brandon Benvie]

I've been following your progress on the port to use CEF and allow use on all platforms. I was curious, have you been successful in making it work under CEF? Or is it still a work-in-progress to get that functional?

[Roger]

Thanks for your interest. Yeah, it's working under Linux & windows now. Most of the source code has been pushed to my github account. OSX is still WIP but it will be soon.

Sent from my phone.

Roger

---

From: Brandon Benvie <brandon...@gmail.com>
Sent: Sun Apr 22 10:04:25 格林尼治标准时间+0800 2012
To: node-...@googlegroups.com
Subject: [node-webkit] CEF Version

[Brandon Benvie]

Yeah I've got all the repos set up in their places and am going to try and compile today (Windows).

[Roger WANG]

Brandon Benvie <brandon...@gmail.com> writes:

> Yeah I've got all the repos set up in their places and am going to try and
> compile today (Windows).

Thanks! As we are still finalizing the source code and pushing them
online, you may find some issues building it on Windows. But most(99%) of the
code has been on github. I'll try to push all the code, write document ASAP
so it would be easier to build and test.

Anyway, if you have any questions, please feel free to ask here.

--
Roger WANG Intel Open Source Technology Center

[Brandon Benvie]

That would be great! I've been waiting for you to come out with this, I knew you'd eventually switch over to CEF because it's the natural choice. I plan to do a lot with this!

I have built CEF and Chromium many, many times, so I have a good knowledge of how to work with this. What's the build order here? Should I just do `gclient runhooks` and then build using nwebkit's gyp file? Or run CEF's build process first? Or something else. I have all the repos in the right places. cef, googleurl, node, node-webkit, openssl, v8, libuv.

[Roger WANG]

Brandon Benvie <brandon...@gmail.com> writes:

Just build CEF as the normal way. It will try to link with Node and
build the node-webkit module. The nwebkit module file need to be
manually relocated after build.

After that you can try to run 'cefclient <path to test html file>'

[Brandon Benvie]

I think the node repo might need to be updated. The gyp file is still pointing to the linux ssl which doesn't work on Windows, and I'm pretty sure you fixed that. Can't get the openssl dependency to work right for generating the project files though.

[Roger WANG]

Brandon Benvie <brandon...@gmail.com> writes:

Right. That need to be guarded with a condition. Currently I'm examining
all windows specific modifications (all of them are in gyp files I
believe). Will update the repo once I found any.

[Roger WANG]

Roger WANG <roger...@intel.com> writes:

Now all the code has been updated. The built cefclient binary can load
'testfs.html' in node-webkit successfully.

The 'nwebkit' module still needs to be worked on though.

[Brandon Benvie]

Yeah it looks like you fixed up most of the issues I was having with building. Chromium is such a huge build that it's hard to tell whether things breaking are because I did something wrong or because they're actually broken. =D I'm going to take another try building today with those updates and see how it works.

[Roger WANG]

Thanks. We'll also provide binary downloads once the OSX port is done.

[Brandon Benvie]

Ok, I finally got it all to compile on Windows 7 64bit (32 bit build). Got the right revisions of everything (harder than it seems!). build/cefclient.exe works correctly. However after many attempts, many variations and attempts to fix it, requiring the nwebkit.dl l (also tried with building as nwebkit.node). The errors are inconclusive, but I have seen both of the following "Error: The specified module could not be found" as if some dll dependency is missing (perhaps something to do with libuv or node? since cefclient.exe works).

When I attach debugging via Visual Studio 2011 the error listed just as node loads nwebkit is a memory access error, but I don't know how to trace it to more detail. It loads into the nwebkit assembly seemingly correctly, and then fails with access errors as it begins to load CEF and Chromium/Webkit.

[Roger]

nwebkit module is not working yet. but load testfs.html from url bar or command line should work.

sent from my phone.

Roger

---

From: Brandon Benvie <brandon...@gmail.com>

Sent: Thu Apr 26 19:33:50 格林尼治标准时间+0800 2012
To: node-...@googlegroups.com
Subject: Re: [node-webkit] Re: CEF Version

[Brandon Benvie]

Oh yes, I see. Cefclient loading node works, but node loading CEF still needs some work. Got it =D. Still enough to start working with! Thanks.

[Brandon Benvie]

Hey, just posting this stuff in case it helps you with debugging. I'm not expecting support or help, I know this isn't even ready yet! But I figured if I have any kind of potentially useful debug info it might be helpful to you.

'cefclient.exe' (Win32): Loaded 'C:\dl\nwebkit\src\build\Release\cefclient.exe'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntdll.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\kernel32.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\KernelBase.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\user32.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\gdi32.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\lpk.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\usp10.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcrt.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\advapi32.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sechost.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\rpcrt4.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sspicli.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cryptbase.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\dl\nwebkit\src\build\Release\libcef.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\winhttp.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\webio.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ws2_32.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\nsi.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\winmm.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\shlwapi.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\comdlg32.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\shell32.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ole32.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\dl\nwebkit\src\build\Release\v8.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcr100.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\userenv.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\profapi.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\urlmon.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\oleaut32.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\iertutil.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\wininet.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\normaliz.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\version.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\psapi.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\imm32.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msctf.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\oleacc.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\setupapi.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cfgmgr32.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\devobj.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\secur32.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\crypt32.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msasn1.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\IPHLPAPI.DLL'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\winnsi.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\dl\nwebkit\src\build\Release\icudt.dll'. Module was built without symbols.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\uxtheme.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dwmapi.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\wintrust.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\clbcatq.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\WinSATAPI.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dxgi.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\winsxs\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_72d18a4386696c80\GdiPlus.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msxml6.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dhcpcsvc6.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dhcpcsvc.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\credssp.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\apphelp.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\nlaapi.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\mswsock.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\WSHTCPIP.DLL'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\wship6.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dnsapi.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Program Files (x86)\Common Files\microsoft shared\Windows Live\WLIDNSP.DLL'. Cannot find or open the PDB file.

'cefclient.exe' (Win32): Loaded 'C:\Program Files (x86)\Bonjour\mdnsNSP.dll'. Cannot find or open the PDB file.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\rasadhlp.dll'. Symbols loaded.

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\FWPUCLNT.DLL'. Symbols loaded.

The thread 0x1248 has exited with code 0 (0x0).

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msctf.dll'. Symbols loaded.

'cefclient.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\msctf.dll'

'cefclient.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msctf.dll'. Symbols loaded.

'cefclient.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\msctf.dll'

First-chance exception at 0x7667B9BC (KernelBase.dll) in cefclient.exe: 0x000006BA: The RPC server is unavailable.

First-chance exception at 0x7667B9BC (KernelBase.dll) in cefclient.exe: 0x000006BA: The RPC server is unavailable.

First-chance exception at 0x7667B9BC (KernelBase.dll) in cefclient.exe: 0x000006BA: The RPC server is unavailable.

First-chance exception at 0x7667B9BC (KernelBase.dll) in cefclient.exe: 0x000006BA: The RPC server is unavailable.

The thread 0xe58 has exited with code 0 (0x0).

First-chance exception at 0x7667B9BC (KernelBase.dll) in cefclient.exe: 0x000006BA: The RPC server is unavailable.

First-chance exception at 0x7667B9BC (KernelBase.dll) in cefclient.exe: 0x000006BA: The RPC server is unavailable.

First-chance exception at 0x7667B9BC (KernelBase.dll) in cefclient.exe: 0x000006BA: The RPC server is unavailable.

First-chance exception at 0x7667B9BC (KernelBase.dll) in cefclient.exe: 0x000006BA: The RPC server is unavailable.

The thread 0xed4 has exited with code 0 (0x0).

[Roger]

thanks for the info.

did this happen when trying to load the nwebkit module?

---

From: Brandon Benvie <brandon...@gmail.com>

Sent: Thu Apr 26 20:35:34 格林尼治标准时间+0800 2012

To: node-...@googlegroups.com
Subject: Re: [node-webkit] Re: CEF Version

[Brandon Benvie]

No, this happens when using either cefclient URL bar "testfs" or "testfs.html" or command line launching "cefclient testfs.html" (with testfs.html in the same directory)

[Roger]

On Thu, Apr 26, 2012 at 8:53 PM, Brandon Benvie <brandon...@gmail.com> wrote:

No, this happens when using either cefclient URL bar "testfs" or "testfs.html" or command line launching "cefclient testfs.html" (with testfs.html in the same directory)

It's supposed to work. Did you give the full URL (e.g. file://C:/ful/path/to/testfs.html) ?

Roger

[Brandon Benvie]

Oh yes, you're right. Full disk URL does work! file:///C:/dl/nwebkit/src/build/Release/testfs.html

Awesome, I'm going to play with this then! Thanks!