If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

First build experience is dreadful

NEW
Unassigned

Status

()

Core
Build Config
2 years ago
2 years ago

People

(Reporter: glandium, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
I was setting up a new VM with VS2015, and here's what I did:
- install VS2015 (which, BTW, now requires manual selection to have everything needed to build Firefox. I don't remember I had to specifically pick the C++ compiler (!) when installing 2013)
- install mozillabuild
- clone m-c

This is where things started to be really uselessfully painful:
- mach build
  -> failed because mercurial is not configured
- mach mercurial-setup
  -> waits 20 seconds in the extraordinary case the person would want to use a directory other than ~/.mozbuild for something that, months after the directory was added, still stores nothing there.
- mach mercurial-setup
  -> asks way too many questions, some of which even feel redundant with the default configuration we have in mozillabuild
- mach build
  -> finally could start building!
(Reporter)

Comment 1

2 years ago
(In reply to Mike Hommey [:glandium] from comment #0)
>   -> waits 20 seconds in the extraordinary case the person would want to use
> a directory other than ~/.mozbuild for something that, months after the
> directory was added, still stores nothing there.

Heh, in fact, mach mercurial-setup puts stuff there now...

Comment 2

2 years ago
I'd love to do most of this stuff automatically. But user choice and all that.

mach mercurial-setup and the mozbuild directory foo on first run is a bit annoying. Especially the 20s pause.

I'd rather see us move towards a "first run wizard" that handles everything from version control configuration, cloning mozilla-central, and creating a mozconfig.
You need to log in before you can comment on or make changes to this bug.