gclient sync without running gyp?

[Fabrice de Gans-Riberi]

Hello wise folks,

Everytime I run gclient sync, gyp insists on running for the default out/ directory. However, I rarely, if ever, actually use that directory and have a bunch of custom output directories for different configurations on which I manually regenerate stuff if I need.

Is there a way to tell gclient to synchronize but not run gyp? This makes me sad every time:

Hook '/usr/bin/python src/build/gyp_chromium' took 25.79 secs

Thanks!

Fabrice

[Bernhard Bauer]

`gclient sync --nohooks`.

Bernhard.

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

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

[Fabrice de Gans-Riberi]

Thanks a lot!
This only seems to be mentioned on the deprecated instructions page on the chromium website. I'm going to see if I can manage to add it in a few other places.

[Thiago Farina]

On Wed, Mar 25, 2015 at 9:16 AM, Fabrice de Gans-Riberi <fde...@chromium.org> wrote:

Thanks a lot!
This only seems to be mentioned on the deprecated instructions page on the chromium website. I'm going to see if I can manage to add it in a few other places.

On Wed, Mar 25, 2015 at 1:06 PM, Bernhard Bauer <bau...@google.com> wrote:

`gclient sync --nohooks`.

Bernhard.

On Wed, Mar 25, 2015 at 12:05 PM Fabrice de Gans-Riberi <fde...@chromium.org> wrote:

Hello wise folks,

Everytime I run gclient sync, gyp insists on running for the default out/ directory. However, I rarely, if ever, actually use that directory and have a bunch of custom output directories for different configurations on which I manually regenerate stuff if I need.

Is there a way to tell gclient to synchronize but not run gyp? This makes me sad every time:

Hook '/usr/bin/python src/build/gyp_chromium' took 25.79 secs

If you want to avoid only the gyp step, you can run it like this:

GYP_CHROMIUM_NO_ACTION=1 gclient sync

--

Thiago Farina

[Fabrice de Gans-Riberi]

On Wed, Mar 25, 2015 at 1:22 PM, Thiago Farina <tfa...@chromium.org> wrote:

If you want to avoid only the gyp step, you can run it like this:

GYP_CHROMIUM_NO_ACTION=1 gclient sync

 

Thanks, that's even better! Adding that to the build instructions too.

[Primiano Tucci]

gclient sync --no-hooks will skip ALL the hooks, not just gyp.

This means that you will not get compiler rolls, landmines, stale LASTCHAGNE etc.

If you want to persistently skip gyp, what you can do is adding the following to your .gclient. It will skip just the gyp_chromium step

solutions = [

{

  'name': 'src',

  ...

  'custom_hooks' : [

   {'name':'gyp', 'action': ['true']},

  ],

--

[Nico Weber]

Please don't. The build instructions should document the regular way of doing things, and the defaults should work well for most people. If we add every possible flag to the build instructions, they'll become the inscrutable mess they were before they got cleaned up recently.

[Fabrice de Gans-Riberi]

On Wed, Mar 25, 2015 at 6:11 PM, Nico Weber <tha...@chromium.org> wrote:

On Wed, Mar 25, 2015 at 5:33 AM, Fabrice de Gans-Riberi <fde...@chromium.org> wrote:

On Wed, Mar 25, 2015 at 1:22 PM, Thiago Farina <tfa...@chromium.org> wrote:

If you want to avoid only the gyp step, you can run it like this:

GYP_CHROMIUM_NO_ACTION=1 gclient sync

 

Thanks, that's even better! Adding that to the build instructions too.

Please don't. The build instructions should document the regular way of doing things, and the defaults should work well for most people. If we add every possible flag to the build instructions, they'll become the inscrutable mess they were before they got cleaned up recently.

Should we add some more "advanced" configuration options on some page somewhere then? This specific flag seems to not be documented anywhere, same with custom_hooks.