Manual Build for 32 bit

Having problems with building or using the JCEF Java binding? Ask your questions here.

Re: Manual Build for 32 bit

Postby relson12 » Wed Jun 03, 2015 7:40 am

Ok, I verified that the directory mirrored yours and after running the hooks, I tried to build the jcef.sln but it errored out and said that it couldn't open any of the source library files and also outputted

LNK1104: cannot open file '.\third_party\cef\\Debug\libcef.lib
relson12
Techie
 
Posts: 23
Joined: Mon May 18, 2015 7:56 pm

Re: Manual Build for 32 bit

Postby magreenblatt » Wed Jun 03, 2015 8:27 am

relson12 wrote:LNK1104: cannot open file '.\third_party\cef\\Debug\libcef.lib

Did you set the jcef_platform value via GYP_DEFINES?
magreenblatt
Site Admin
 
Posts: 12409
Joined: Fri May 29, 2009 6:57 pm

Re: Manual Build for 32 bit

Postby relson12 » Wed Jun 03, 2015 8:40 am

Normally before I run the gclient runhooks, I have to edit the make version_header.py file and comment out the platform while adding in platform="win32". Otherwise, it will throw an error.

I have the following System Environmental Variables.
GYP_DEFINES
Value: jcef_platform= win32 jdk_directory="C:\Java\jdk1.7.0_67"

GYP_MSVS_VERSION
Value: 2010
relson12
Techie
 
Posts: 23
Joined: Mon May 18, 2015 7:56 pm

Re: Manual Build for 32 bit

Postby relson12 » Wed Jun 03, 2015 10:13 am

Good news Marshall, I was successful in getting the jcef.sln to build. However, there are still two cefclient.sln files. Should I be trying to build the 2010 one that originally came with CEF3 or the new cefclient one? The 2010 builds fine but the new one outputs MSB6006 cmd exited with code 4 on both cefclient and cefsimple.
relson12
Techie
 
Posts: 23
Joined: Mon May 18, 2015 7:56 pm

Re: Manual Build for 32 bit

Postby magreenblatt » Wed Jun 03, 2015 10:26 am

relson12 wrote:Value: jcef_platform= win32 jdk_directory="C:\Java\jdk1.7.0_67"

If there's a space between jcef_platform= and win32 as shown here then that could likely be your problem.
magreenblatt
Site Admin
 
Posts: 12409
Joined: Fri May 29, 2009 6:57 pm

Re: Manual Build for 32 bit

Postby relson12 » Wed Jun 03, 2015 10:26 am

Actually nevermind, both cefclient files are outputting that error.
relson12
Techie
 
Posts: 23
Joined: Mon May 18, 2015 7:56 pm

Re: Manual Build for 32 bit

Postby relson12 » Wed Jun 03, 2015 10:34 am

Yes, I started from scratch, set the environmental variables via the path to jcef in the command line and everything worked fine. The javacef.sln file compiled correctly. The cefclient.sln files are the problem now. Neither will build without outputting the MSB6006 error cmd exited with code 4.
relson12
Techie
 
Posts: 23
Joined: Mon May 18, 2015 7:56 pm

Re: Manual Build for 32 bit

Postby magreenblatt » Wed Jun 03, 2015 11:43 am

relson12 wrote:Yes, I started from scratch, set the environmental variables via the path to jcef in the command line and everything worked fine. The javacef.sln file compiled correctly. The cefclient.sln files are the problem now. Neither will build without outputting the MSB6006 error cmd exited with code 4.

Yeah, that's expected. You can't build cefclient with the output of running GYP for JCEF.
magreenblatt
Site Admin
 
Posts: 12409
Joined: Fri May 29, 2009 6:57 pm

Re: Manual Build for 32 bit

Postby relson12 » Fri Jun 05, 2015 7:23 am

I was able to build CEF3 by moving the win32 folder outside of the javacef directory and onto my desktop. I noticed there are java files such as Cef Browser Factory, and CefApp now. Did these replace Chromium, DownloadWindow, ChromeSettings, ChromeWindow, SampleBrowser etc. or am I missing a step and all of these should once again be present?
relson12
Techie
 
Posts: 23
Joined: Mon May 18, 2015 7:56 pm

Re: Manual Build for 32 bit

Postby magreenblatt » Tue Jun 09, 2015 4:07 pm

magreenblatt wrote:Sounds like your directory structure might be wrong. This is what it should look like:

Code: Select all
java-cef/
  .git/
  .gclient
  src/
    build/
    java/
    native/
    third_party/
    tools/
    jcef.gyp
    jcef.sln
    ...


Run gclient from the top-level java-cef directory.

Newer versions of depot_tools were downloading the src directory twice (so you'd end up with a src/src directory). This has been fixed in https://bitbucket.org/chromiumembedded/ ... /issue/170. See the updated BranchesAndBuilding Wiki page.
magreenblatt
Site Admin
 
Posts: 12409
Joined: Fri May 29, 2009 6:57 pm

PreviousNext

Return to JCEF Forum

Who is online

Users browsing this forum: No registered users and 133 guests