oxide team mailing list archive

[Olivier Tilloy <olivier.tilloy@xxxxxxxxxxxxx>]

On Fri, May 2, 2014 at 10:11 AM, Chris Coulson <chrisccoulson@xxxxxxxxxx>wrote:

>  On 02/05/14 06:38, Olivier Tilloy wrote:
>
>
>
>
> On Thu, May 1, 2014 at 11:17 AM, Chris Coulson <chrisccoulson@xxxxxxxxxx>wrote:
>
>> Hi,
>>
>> Chad Miller noticed last week that Google have stopped supporting the
>> GYP makefile backend for building Chromium. Running ./build/gyp_chromium
>> now results in an error (see
>>
>> https://chromium.googlesource.com/chromium/src/build/+/9bc1c207a18ffa8284095d9350e835a4518870f6
>> ).
>> However, we don't use this script so makefile builds still work (sort-of).
>>
>> There has been 2 makefile-specific build breakages in the last couple of
>> weeks that have gone unfixed - 1 of these we are now carrying a Chromium
>> patch for and the other one required a build config tweak to work
>> around. I plan to push a change shortly that makes Oxide build the
>> Chromium parts with GYP's ninja backend instead, which is the only
>> officially supported backend for building Chromium on Linux.
>>
>
>  Does this buy us shorter build times by any chance?
> That would be a nice side effect :)
>
>
>  Hi,
>
> I wouldn't expect it to have much of an effect on overall build times, but
> it has drastically improved the no-op build time (it's less than 1 second
> for me now).
>

Well, that’s already a huge win!
I also notice that on a full chromium build the progress is easier to track
with an indicator of how many files have already been compiled and their
total number. Small but welcome improvement.