I got it to work by removing the "-l 10" from my ninja build command. I got the build command from Simple Chrome Workflow.What does the "-l 10" flag do?
I got it to work by removing the "-l 10" from my ninja build command. I got the build command from Simple Chrome Workflow.What does the "-l 10" flag do? Should the workflow page be updated to have it removed?--On Mon, Oct 16, 2017 at 4:04 PM, Simon Que <sq...@chromium.org> wrote:I have two different build directories in my Chromium checkout.One is under out_buddy/Release, which I use to build Chrome for deployment to Chrome OS.The other is under out/Debug, which I use for more generic Chrome developmentWhen I attempt to build Chrome in out/Debug, it builds rapidly, since it uses goma.
But when I attempt to build Chrome in out_buddy/Release, it builds slowly, seemingly not using goma. It built with goma last week. The gn args are the same as before. The only change was that I synced my Chromium checkout. But the other dir (out/Debug) should also be affected by this, but it clearly builds with goma.I am trying to figure out why it only builds one dir with goma and the other without.Simon
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CANV8Hs32mGa1vhFt4O5JcPTgmO9w2m8aJLdbKxQdio0djaQhew%40mail.gmail.com.