Remove gyp support

Bug #1589902 reported by Chris Coulson on 2016-06-07
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Chris Coulson

Bug Description

Once the GN build is working fine and we can produce packages with it, we should drop the gyp build files (assuming Chromium hasn't done so already)

Changed in oxide:
importance: Undecided → Medium
status: New → Triaged
Changed in oxide:
milestone: none → branch-1.17
Chris Coulson (chrisccoulson) wrote :

Let's defer this to 1.18 in case we need to switch back close to the release

Changed in oxide:
milestone: branch-1.17 → branch-1.18
Chris Coulson (chrisccoulson) wrote :

I'm not sure if this can be deferred - the gyp build of Chromium is already broken, and it's no longer possible to build Oxide with it

Changed in oxide:
status: Triaged → In Progress
assignee: nobody → Chris Coulson (chrisccoulson)
Chris Coulson (chrisccoulson) wrote :
Changed in oxide:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers