Export to GitHub

chromiumembedded - issue #1573

Automated git build generates cefclient/CMakeLists.txt with unresolved macros


Posted on Mar 10, 2015 by Happy Giraffe

This is probably a follow-on to bug 1404.

What steps will reproduce the problem? 1. On MacOSX 10.9, get and build trunk:

$ wget https://chromiumembedded.googlecode.com/svn/trunk/cef3/tools/automate/automate-git.py

$ python automate-git.py --download-dir=$HOME/dsrc --x64-build

  1. Unpack and try to build cefclient:

$ unzip chromium/src/cef/binary_distrib/cef_binary_3.2321.2053_macosx64.zip $ cd cef_binary_3.2321.2053_macosx64/cefclient $ mkdir btmp $ cd btmp $ cmake ..

  1. cmake fails with

CMake Error at CMakeLists.txt:230 (APPEND_PLATFORM_SOURCES): Unknown CMake command "APPEND_PLATFORM_SOURCES".

There are other internal macros; if you copy in APPEND_PLATFORM_SOURCES as was done elsewhere by http://code.google.com/p/chromiumembedded/source/detail?r=1886 it still fails with

CMake Error at CMakeLists.txt:271 (ADD_LOGICAL_TARGET): Unknown CMake command "ADD_LOGICAL_TARGET".

Apologies if I'm missing something obvious, I literally just ran the automated build for the first time today, and know very very little about the build these days. (I'm trying to get set up to make a small change to how icudtl.dat is found, kind of like http://code.google.com/p/javachromiumembedded/issues/detail?id=109, and figured trunk was the place to do it. )

Comment #1

Posted on Mar 10, 2015 by Quick Horse

You need to run CMake from the top-level directory (cef_binary_3.2321.2053_macosx64) and pass specific defines to CMake. See comments in the top-level CMakeLists.txt file for usage.

Comment #2

Posted on Mar 11, 2015 by Happy Giraffe

Yeah, I figured that out in my sleep last night.

I was just used to the xcodebuild for cefclient standing alone, and didn't think that it might have been glommed into an overall build during the transition to cmake.

Status: WontFix

Labels:
Type-Defect Priority-Medium