Closed Bug 1487505 Opened 6 years ago Closed 6 years ago

Run `tup init` in the closest common ancestor of the srcdir and the active objdir

Categories

(Firefox Build System :: General, enhancement)

enhancement
Not set
normal

Tracking

(firefox64 fixed)

RESOLVED FIXED
mozilla64
Tracking Status
firefox64 --- fixed

People

(Reporter: chmanchester, Assigned: chmanchester)

References

Details

Attachments

(1 file)

When building the backend we run `tup init` if necessary in the topsrcdir. The ensuing build will fail if the topobjdir is outside of the topsrcdir. There several workflows here that may be hard to fully support, but at least in simple instances of this case we can just run `tup init` in the closest common ancestor of the srcdir and objdir.
Comment on attachment 9005776 [details]
Bug 1487505 - Prompt user to run `tup init` in an appropriate location when building an objdir outside of the srcdir in tup.

Michael Shal [:mshal] has approved the revision.
Attachment #9005776 - Flags: review+
Pushed by cmanchester@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/bb4d2474abdf
Prompt user to run `tup init` in an appropriate location when building an objdir outside of the srcdir in tup. r=mshal
https://hg.mozilla.org/mozilla-central/rev/bb4d2474abdf
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: