Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upRegression in CEF build time #13591
Closed
Regression in CEF build time #13591
Labels
Comments
|
Oh, duh, #1 won't work because we set this flag in both linux-rel builders :-) |
bors-servo
added a commit
that referenced
this issue
Oct 5, 2016
Ensure that SERVO_ENABLE_DEBUG_ASSERTIONS is also used in build-cef r? @nox Fixes #13591 This fixes the problem with rebuilding all of CEF on the linux-rel builders by ensuring it gets the same `RUSTFLAGS`. Proof: ``` [larsberg@larsberg servo2]$ ./mach build-cef -r Compiling embedding v0.0.1 (file:///Users/larsberg/servo2/ports/cef) Finished release [optimized] target(s) in 35.42 secs [Warning] Could not generate notification! Optional Python module 'pyobjc' is not installed. CEF build completed in 0:00:38 [larsberg@larsberg servo2]$ ``` <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/13601) <!-- Reviewable:end -->
|
Thanks for taking care of this Lars! I meant to get to this today but I On Wed, Oct 05, 2016 at 09:10:36AM -0700, bors-servo wrote:
|
|
np! It was so easy that even I could do it :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As of http://build.servo.org/builders/linux-rel-css/builds/23, the CEF build now rebuilds the entire tree. This is due to:
19a5a30#diff-4b02cf15724590179b4a5025f1a81a0dR223
With that line, I believe that the default release build and the CEF build have different
-Cflags. There are a few options here:It seems like #2 might be useful if we think we will start testing CEF, but #1 is definitely the easy one :-)
CC @nox @emilio