[meta] Easier implementation of alternative build backends

RESOLVED FIXED

Status

defect
RESOLVED FIXED
7 years ago
a year ago

People

(Reporter: gps, Unassigned)

Tracking

(Depends on 6 bugs, Blocks 1 bug, {meta})

Trunk
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Reporter

Description

7 years ago
A lot of people are interested in prototyping alternate build backends for mozilla-central. It is difficult to do this today because our build system makes a lot of assumptions about there being only one build backend: recursive make files.

This tracking bug should be blocked by all bugs that stand in the way of making alternate build backends difficult to implement.

At this juncture, the main issues are:

1) Ensuring the build config files (typically Makefile.in's) consist of only simple variable assignment and no make-isms. This makes them easily machine readable, facilitating other build backends to extract information and do whatever they want with it.

2) Ensuring things like autoconf/configure are flexible and allow alternate build backends. e.g. configure today always writes Makefiles. Pieces need to be configurable and not assume Makefiles are the only show in town.
Reporter

Updated

7 years ago
Depends on: 774106
Reporter

Updated

7 years ago
Depends on: 774381
Reporter

Updated

7 years ago
Depends on: 774572
Reporter

Updated

7 years ago
Depends on: 774691
Depends on: 780460
Reporter

Updated

7 years ago
Depends on: 784841
Reporter

Updated

7 years ago
Depends on: 785740
Summary: [meta] Easier implementation of alternate build backends → [meta] Easier implementation of alternative build backends
Reporter

Updated

6 years ago
No longer depends on: 774381
Blocks: buildtup
Reporter

Updated

2 years ago
Depends on: 1412398
Reporter

Updated

2 years ago
Depends on: 1416297

Updated

a year ago
Product: Core → Firefox Build System
We've done a lot of work in this area, I don't think we're going to end up using this as a tracking bug.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.