On 10/30/13, 2:55 AM, Neil wrote:
Gregory Szorc wrote:
OK, so you run make, make.py, or mozmake to build the tree. Do you
ever perform partial tree builds? That is: |make -C dom| or |cd dom;
make|. If so, you may be impacted by a recent change to the build system.
If you attempt to perform a p
Gregory Szorc wrote:
OK, so you run make, make.py, or mozmake to build the tree. Do you
ever perform partial tree builds? That is: |make -C dom| or |cd dom;
make|. If so, you may be impacted by a recent change to the build system.
If you attempt to perform a partial tree build directly with a
On Tue, Oct 29, 2013 at 03:47:40PM -0700, Aki Sasaki wrote:
> There *may* be l10n fallout here due to a |cd config; make| and a
> followup |hg update -r REVISION| afterwards (IIRC)... let's keep an eye
> on that.
Those builds should have a step running either configure or
config.status after hg up
There *may* be l10n fallout here due to a |cd config; make| and a
followup |hg update -r REVISION| afterwards (IIRC)... let's keep an eye
on that.
https://bugzilla.mozilla.org/show_bug.cgi?id=925720 is on my radar but
between vcs-sync, releases, and merge week, haven't yet had a chance to
look at
If you use |mach build| to build the tree, stop reading: this post does
not apply to you.
OK, so you run make, make.py, or mozmake to build the tree. Do you ever
perform partial tree builds? That is: |make -C dom| or |cd dom; make|.
If so, you may be impacted by a recent change to the build sy
5 matches
Mail list logo