Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Build changes upcoming: libxul will be required, and IPC will be required

55 views
Skip to first unread message

Benjamin Smedberg

unread,
Mar 4, 2011, 8:54:16 AM3/4/11
to mozilla.dev.planning group, dev-pl...@lists.mozilla.org
When the tree is open for the next release, we have several build
changes which have been long-planned and are now coming to fruition:

The libxul build configuration will be the only supported configuration:
--disable-libxul will throw an error.
The IPC build configuration will be required, --disable-ipc will throw
an error.

The necessary prerequisite for requiring libxul was fixing the build
speed on mac, where relinking libxul took minutes. That has been fixed
in bug 535897, which has already landed in the build-system project
branch. Quoth bz:

> I tried that branch. Takes the incremental build time (for a manual
> build in
> the relevant dir, layout/build, and toolkit/library) for a minor change to
> content/layout code from about 130 seconds to about 10 seconds on my
> hardware.
> I can live with that!

IPC was an optional component mainly because it required libxul. Now
that we can require libxul across the board, code maintenance will be
much simpler if we can also assume that IPC is available across the board.

Reference bugs:
Fixing build speed on mac:
https://bugzilla.mozilla.org/show_bug.cgi?id=535897
Disallow --disable-libxul:
https://bugzilla.mozilla.org/show_bug.cgi?id=638429
Disallow --disable-ipc: https://bugzilla.mozilla.org/show_bug.cgi?id=638755

Please direct followup comments to mozilla.dev.platform.

--BDS

Mark Banner

unread,
Mar 4, 2011, 4:34:29 PM3/4/11
to
On 04/03/2011 13:54, Benjamin Smedberg wrote:
> When the tree is open for the next release, we have several build
> changes which have been long-planned and are now coming to fruition:

When do we expect the tree to re-open?

Thunderbird is probably only a patch or two away from being able to
include IPC and not break.

However, I'd really like an indication so that I can plan to get that
finished and landed (i.e. 2 days, 1 week, 2 weeks? just something
approximate).

Standard8

Justin Wood (Callek)

unread,
Mar 4, 2011, 9:46:14 PM3/4/11
to

Well in the short term the build-system changes (like that) are landing
in http://hg.mozilla.org/projects/build-system with
http://tbpl.mozilla.org/?tree=Build-System as the tbpl.

Some prelim stuff for this change has already landed if I remember
correctly.

I think ted/khuey might be willing to let you take any IPC m-c patches
(that already have reviews) on that branch so you can test against that
change, but I am surely not the deciding force there.

--
~Justin Wood (Callek)

Benjamin Smedberg

unread,
Mar 4, 2011, 11:41:38 PM3/4/11
to Mark Banner, dev-pl...@lists.mozilla.org
On 3/4/2011 4:34 PM, Mark Banner wrote:
> On 04/03/2011 13:54, Benjamin Smedberg wrote:
>> When the tree is open for the next release, we have several build
>> changes which have been long-planned and are now coming to fruition:
>
> When do we expect the tree to re-open?
Currently the tree remains restricted for Firefox 4 Mobile work. This
cannot possibly change until next Friday at the earliest, because we
will not unfreeze Firefox nightlies until after the release candidate is
shipped. We're probably talking 1.5-2 weeks.

--BDS

Kyle Huey

unread,
Mar 4, 2011, 11:45:55 PM3/4/11
to Justin Wood (Callek), dev-pl...@lists.mozilla.org
Landing these patches in bs is fine as long as they're not going to be a
complete PITA to merge back. I'm hoping to get to the front of the line for
landing after m-c reopens so hopefully that won't be a big deal.

- Kyle

> _______________________________________________
> dev-planning mailing list
> dev-pl...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-planning
>

0 new messages