Unable to set up GN build

[Simon Que]

I tried to create a GN build directory by running "gn gen out_linux/gn" from the chromium src/ directory. I got the following message. I have previously been able to do a GN build with no problems.

Simon

=====================================================

ERROR at //build/config/linux/pkg_config.gni:85:17: Script returned non-zero exit code.

    pkgresult = exec_script(pkg_config_script, args, "value")

                ^----------

Current dir: /usr/local/ssd/cros/chromium/src/out_linux/gn/

Command: python /usr/local/ssd/cros/chromium/src/build/config/linux/pkg-config.py -s /usr/local/ssd/cros/chromium/src/build/linux/debian_wheezy_amd64-sysroot -a x64 --system_libdir lib pangocairo

Returned 1.

stderr:

Package xdmcp was not found in the pkg-config search path.

Perhaps you should add the directory containing `xdmcp.pc'

to the PKG_CONFIG_PATH environment variable

Package 'xdmcp', required by 'XCB', not found

Could not run pkg-config.

See //build/config/linux/BUILD.gn:49:1: whence it was called.

pkg_config("pangocairo") {

[Lei Zhang]

Does build/linux/debian_wheezy_amd64-sysroot exist? build/linux/debian_wheezy_amd64-sysroot/usr/lib/pkgconfig/xdmcp.pc ?

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Simon Que]

No. The directory exists but it doesn't contain that file.

[Thiago Farina]

On Tuesday, February 2, 2016, Simon Que <sq...@chromium.org> wrote:

No. The directory exists but it doesn't contain that file.

Is this a checkout of 'fetch chromium'? gclient runhooks usually get

things like the sysroot for you.

 

--

Thiago Farina

[Simon Que]

Oh I didn't run "gclient runhooks" after a "gclient sync". I usually just skip to running build/gyp_chromium.

That fixed it, thanks.

[Lei Zhang]

gclient sync usually does gclient runhooks at the end, but maybe you
turned it off with --nohooks or something.

Are you avoiding runhooks because it runs GYP at the end? I think
that's actually the slowest part of runhooks. If you are using GN and
trying to avoid running GYP as part of runhooks, the way to do that is
with the GYP_CHROMIUM_NO_ACTION env var.

[Simon Que]

I was avoiding it because I am passing in my own GYP_DEFINES to build/gyp_chromium.

[Lei Zhang]

You can pass GYP_DEFINES to gyp_chromium via gclient sync or gclient
runhooks. You don't have to avoid runhooks because you have custom
GYP_DEFINES.