Re: Avoiding the hard build dependency on NodeJS

I wonder if ChakraCore (the JS engine used inside Edge) has a JavaScript interpreter that would make it viable to run node-chakracore ( https://github.com/nodejs/node-chakracore) to run on sparc64. Have you tried that by any chance? (Of course even if that works, how compatible the node_modules u

Re: Builds docs on MDN

On 06/22/2017 12:11 AM, ISHIKAWA,chiaki wrote: (I am posting a response to Ehsan's message which somehow was garbled and he kindly corrected in a personal exchange.) On 2017/06/22 6:10, Ehsan Akhgari wrote: Oops, not sure how that happened, sorry about that! But that formatting corru

Re: Builds docs on MDN

is a real issue, and is a very easy one to solve for out of tree docs incidentally with a simple moz.build annotation similar to BUG_COMPONENT, I think. On Wed, Jun 21, 2017 at 12:50 PM, ISHIKAWA,chiaki > mailto:ishik...@yk.rim.or.jp>> wrote: > > On 2017/06/21 2:19, Ehsan Akhgari

Re: Builds docs on MDN

On 06/20/2017 12:55 PM, Benjamin Smedberg wrote: On Tue, Jun 20, 2017 at 12:40 PM, Ehsan Akhgari mailto:ehsan.akhg...@gmail.com>> wrote: On 06/20/2017 11:21 AM, Benjamin Smedberg wrote: Coming in late to this thread, but I'd like to strongly support moving

Re: Builds docs on MDN

the docs living on the different branches (central/beta etc) get treated differently (for example how should one document something that changed on central before the change hits the rest of the channels?), how to preview the edits I'm making, how to subscribe to notifications (similar to

Re: Builds docs on MDN

x27;s blessing beforehand in the first place. :-/ [1]: http://www.yesodweb.com/blog/2015/08/thoughts-on-documentation - Ryan On Fri, Jun 16, 2017 at 10:05 AM, Sylvestre Ledru mailto:sylves...@mozilla.com>> wrote: Le 16/06/2017 à 16:40, Boris Zbarsky a écrit : > On 6/16/17

Re: Builds docs on MDN

FWIW most of my contributions to the documentation hosted on MDN were in the form of casual edits here and there to pages, mostly in the form of me noticing something wrong in some documentation and quickly editing the wiki to fix it. The editing process of the MDN wiki was (well, still is!) e

Re: Optimizing what runs on which push

here for small incremental hacks to improve usability for everyone within this design. Yeah, agreed. (I'm drooling over the --all-failures-from idea!) Thanks for thinking about this use case! Dustin 2017-06-02 18:19 GMT-04:00 Ehsan Akhgari : I haven't really read the thread in too much de

Re: Optimizing what runs on which push

I haven't really read the thread in too much detail so I apologize if what I'll say below is silly or covered elsewhere, but since there seems to be a proposal around replacing the try syntax with machines figuring out what jobs are needed for a push (presumably based on what changed in the pus

Re: Redirecting http://hg.mozilla.org/ to https://

I have two extra suggestions for added security benefits: 1. In order to ensure that clients that support CSP will never attempt to contact the HTTP version of the site for fetching any subresources that may still point to http:, please make sure to serve the |Content-Security-Policy: upgrade-inse

Re: moz.build processing time

On 2016-11-24 7:04 PM, Nathan Froyd wrote: > On Wed, Nov 23, 2016 at 4:31 PM, Mike Hommey wrote: >> I know OSX can be bad with I/O, but that seems unusually bad. IIRC gps >> found that there's a relatively low limit to the number of files or >> inodes that can be in cache, and a working tree of m-

Re: moz.build processing time

On 2016-11-23 4:09 PM, Mike Hommey wrote: > On Wed, Nov 23, 2016 at 01:57:44PM -0500, Ehsan Akhgari wrote: >> Here is mine: >> <https://gist.github.com/ehsan/ad4e56f2d2f70e3e6c578a2517afbc15> > > 12.9s spent in 324 calls to select.select. > 4.8s spent in 43898 calls

Re: moz.build processing time

On 2016-11-22 7:39 PM, Gregory Szorc wrote: > On Mon, Nov 21, 2016 at 2:06 PM, Ehsan Akhgari <mailto:ehsan.akhg...@gmail.com>> wrote: > > On 2016-11-21 1:08 PM, Gregory Szorc wrote: > > On Sat, Nov 19, 2016 at 1:32 PM, Ehsan Akhgari <mai

Re: moz.build processing time

On 2016-11-21 1:08 PM, Gregory Szorc wrote: > On Sat, Nov 19, 2016 at 1:32 PM, Ehsan Akhgari <mailto:ehsan.akhg...@gmail.com>> wrote: > > On 2016-11-19 4:26 PM, Mike Hommey wrote: > > On Sat, Nov 19, 2016 at 04:12:22PM -0500, Ehsan Akhgari wrote: > >&g

Re: moz.build processing time

On 2016-11-19 4:26 PM, Mike Hommey wrote: > On Sat, Nov 19, 2016 at 04:12:22PM -0500, Ehsan Akhgari wrote: >> On 2016-11-18 7:22 PM, Gregory Szorc wrote: >>> On Fri, Nov 18, 2016 at 3:50 PM, Ehsan Akhgari >> <mailto:ehsan.akhg...@gmail.com>> wrote: >>>

Re: moz.build processing time

On 2016-11-18 7:22 PM, Gregory Szorc wrote: > On Fri, Nov 18, 2016 at 3:50 PM, Ehsan Akhgari <mailto:ehsan.akhg...@gmail.com>> wrote: > > Here are the moz.build processing times on my machine when I add one > line to a LOCAL_INCLUDES in one moz.build file: > >

moz.build processing time

Here are the moz.build processing times on my machine when I add one line to a LOCAL_INCLUDES in one moz.build file: 0:02.97 Reticulating splines... 0:37.16 Finished reading 3131 moz.build files in 23.09s 0:37.16 Processed into 9325 build config descriptors in 3.62s 0:37.16 RecursiveMake backe

Re: Cross compile firfox on linux for windows

On 2016-03-08 9:26 AM, wolf.tob...@gmx.net wrote: > Am Dienstag, 8. März 2016 15:21:48 UTC+1 schrieb Tobias: >> Am Montag, 7. März 2016 21:02:39 UTC+1 schrieb Ehsan Akhgari: >>> On 2016-02-11 2:38 AM, w...@gmx.net wrote: >>>> Am Sonntag, 7. Februar 2016 00:25:

Re: Cross compile firfox on linux for windows

On 2016-02-11 2:38 AM, wolf.tob...@gmx.net wrote: > Am Sonntag, 7. Februar 2016 00:25:25 UTC+1 schrieb Ehsan Akhgari: >> On 2016-02-05 1:30 PM, wolf.tob...@gmx.net wrote: >>> Am Donnerstag, 4. Februar 2016 16:35:58 UTC+1 schrieb wolf@gmx.net: >>>> I try to do a

Re: Cross compile firfox on linux for windows

On 2016-02-05 1:30 PM, wolf.tob...@gmx.net wrote: > Am Donnerstag, 4. Februar 2016 16:35:58 UTC+1 schrieb wolf@gmx.net: >> I try to do a cross compile on linux centos 64bit for windows 64 bit. I >> tried as written here >> "https://developer.mozilla.org/en-US/docs/Cross_Compile_Mozilla_for_Mi

Re: Cross compile firfox on linux for windows

On 2016-02-04 10:35 AM, wolf.tob...@gmx.net wrote: > I try to do a cross compile on linux centos 64bit for windows 64 bit. I tried > as written here > "https://developer.mozilla.org/en-US/docs/Cross_Compile_Mozilla_for_Mingw32";. > > but I get always this error and don`t know how to fix it. >

Re: VS2015 Builds won't run on systems without VCRedist installed on them

On 2016-02-03 7:19 PM, Alex wrote: >> How does the binary not run? Do you get an error of some sort? Can you >> please post it here? > >> Did you move all the required DLLs (ucrtbase.dll, api-ms-win-*.dll, >> vcruntime140.dll, msvcp140.dll)? > > As for the issue of the build not running, ther

Re: VS2015 Builds won't run on systems without VCRedist installed on them

(CCing poiru who actually implemented this!) On 2016-02-03 3:36 PM, Alex wrote: I've built changeset f2f8fc172f4c (https://hg.mozilla.org/mozilla-central/file/f2f8fc172f4c). The following two issues still occur: - DLLs from WIN_UCRT_REDIST_DIR="C:/Program Files (x86)/Windows Kits/10/Redist/u

Re: VS2015 Builds won't run on systems without VCRedist installed on them

On 2016-02-03 1:45 PM, Alex wrote: Hi all, I posted about this in bug 1204202 (https://bugzilla.mozilla.org/show_bug.cgi?id=1204202) but that was probably not the correct place to do so. Any builds I make with VS2015 will fail to run on any systems without the VCRedist installed on that syst

Re: Clang compilation databases

On 2015-09-18 6:36 PM, Mike Hommey wrote: On Fri, Sep 18, 2015 at 01:03:15PM -0700, Gregory Szorc wrote: A few people have pinged me recently regarding static analysis and other Clang-based tooling that relies on having a Clang compilation database (the Clang tools use this database so they know

Re: Clang-cl fails to build NSS library on Windows

On 2015-06-25 5:24 PM, Alex wrote: Attempting to compile Firefox with clang-cl works great up until freebl, where it chokes. This is attempting to build a 64-Bit version with 64-Bit clang. Both versions 3.6.0-r225071 and 3.7.0-r240278 were used, but with the same errors from both. I used the

Re: Build system goals for Portland

On 2014-11-26 5:37 PM, Gregory Szorc wrote: I put together https://etherpad.mozilla.org/build-portland-goals to try to capture what people hope to do in Portland with regards to the Firefox build system. If you have something you are trying to drive or you have something you want to extract from

Re: Firefox not compiling on OSX (Universal Build) - No Preprocessor DIrectives

On 2014-10-16, 1:42 PM, digitalc...@gmail.com wrote: 159:49.25 Error: /Users/AaronTravis/mozilla-source/mozilla-beta-aaa4d64b66e5/obj-x86_64-apple-darwin13.4.0/i386/browser/installer/package-manifest:54: Missing file(s): PolyBrowser.app/Contents/MacOS/polybrowser-bin 159:58.44 Traceback (most r

Re: Firefox not compiling on OSX (Universal Build) - No Preprocessor DIrectives

On 2014-10-15, 11:18 PM, digitalc...@gmail.com wrote: I am building Firefox on OSX (Universal Build) and am getting tons of "No Preprocessor" errors like this one... /Users/Aaron/mozilla-source/mozilla-beta-aaa4d64b66e5/dom/webidl/Crypto.webidl: WARNING: no preprocessor directives found Thos

Re: How to pass LDFLAGS to the NSS build system?

OS_DLLFLAGS) $(DLLFLAGS) +LINK_DLL = $(LINK) $(OS_DLLFLAGS) $(DLLFLAGS) -opt:ref,icf -LARGEADDRESSAWARE LINK_EXE = $(LINK) $(OS_LFLAGS) $(LFLAGS) CFLAGS= $(OPTIMIZER) $(OS_CFLAGS) $(XP_DEFINE) $(DEFINES) $(INCLUDES) \ On Tue, Sep 16, 2014 at 9:11 AM, Ehsan Akhgari mailto:ehsan.ak

How to pass LDFLAGS to the NSS build system?

I'm trying to get the AddressSanitizer builds on Windows working. I need to pass in a couple of library names to the linker through a mozconfig setting. Setting them in LDFLAGS in the mozconfig doesn't work because NSS is built with its own LDFLAGS. There is MOZ_CFLAGS_NSS that makes NSS inherit

Re: moderately-sized project ideas for the build system?

On 2014-09-05, 11:05 AM, Gregory Szorc wrote: On 9/5/14 7:27 AM, Ehsan Akhgari wrote: On 2014-09-04, 5:31 PM, Gregory Szorc wrote: On 9/4/14 2:13 PM, Mike Hommey wrote: On Thu, Sep 04, 2014 at 01:25:29PM -0700, Gregory Szorc wrote: There are some things jotted down at https

Re: moderately-sized project ideas for the build system?

On 2014-09-04, 5:31 PM, Gregory Szorc wrote: On 9/4/14 2:13 PM, Mike Hommey wrote: On Thu, Sep 04, 2014 at 01:25:29PM -0700, Gregory Szorc wrote: There are some things jotted down at https://etherpad.mozilla.org/build-system-goals But that hasn't been updated in months. For immediate goals, I

Re: Taking moz.build to the next level

On 2014-09-03, 11:56 PM, Joshua Cranmer 🐧 wrote: The worst offender is the list of source files: it is passed down as a VariablePassthru in CSRCS, CPPSRCS, etc., and UNIFIED_CSRCS, UNIFIED_CPPSRCS, etc. If you want to distinguish between source files in the build directory and source files in the

Build times regressing

Hi everyone, Not sure if anyone watches over our build times, but based on my totally non-scientific benchmarks on my own hardware on Mac, I am now getting a clobber debug build in ~9:30mins, which is around 2 full minutes longer than the build time that I used to get when I finished my work on un

Re: RFC: On making command lines knowable to moz.build

On 2014-05-10, 1:07 AM, Joshua Cranmer 🐧 wrote: One of the most useful things to export to moz.build backends is the ability to represent compile commands faithfully--for example, for things like IDE integration or clang compilation databases. Our moz.build migrations have moved most of the obvio

Re: Building a debug version without optimizations on Windows 7

Unfortunately the build system does not recognize changes to .mozconfig files as a dependency change, so it won't pick them up. In order to make sure your new mozconfig file is really in effect, do a ./mach clobber to delete your object directory before running ./mach build again. Cheers, Ehs

Re: Overhauling MozillaBuild

On 2014-03-12, 5:57 PM, Mike Hommey wrote: On Tue, Mar 11, 2014 at 08:02:31AM -0700, Ryan VanderMeulen wrote: As some of you on this list are already aware of, I have recently been toying with the idea of overhauling MozillaBuild. I'm sending this message out to flesh out the plan more and colle

Re: Please help with bug 973649

On 2/24/2014, 9:37 PM, xunxun wrote: On 2014/2/25 星期二 10:00, Ehsan Akhgari wrote: That bug currently blocks my work in moving the information required to build libxul to moz.build. Thanks! -- Ehsan <http://ehsanakhgari.org/> What's your error when building with the patch? Ple

Please help with bug 973649

That bug currently blocks my work in moving the information required to build libxul to moz.build. Thanks! -- Ehsan ___ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds

Re: CFLAGS in moz.build

the vast majority of those variables just add things like TK_CFLAGS that do not exist in moz.build. I'm ignoring those as well.) -- Ehsan <http://ehsanakhgari.org/> On Sun, Feb 16, 2014 at 10:08 PM, Gregory Szorc wrote: > On 2/16/2014 6:07 PM, Ehsan Akhgari wrote: > >

Re: What is the correct way of reflecting make variables in moz.build?

On 2/17/2014, 3:18 PM, Ms2ger wrote: On 02/17/2014 08:09 PM, Ehsan Akhgari wrote: CFLAGS += $(TK_CFLAGS) I never quite figured out why we didn't just set those flags globally. That seems like a much easier solution. Can you please give an example of what you mean? I don

Re: CFLAGS in moz.build

On Mon, Feb 17, 2014 at 11:46 AM, Joshua Cranmer 🐧 wrote: > On 2/16/2014 8:07 PM, Ehsan Akhgari wrote: > >> What is the plan for porting CFLAGS and friends to moz.build? Is there >> any work in progress for that? How can one help? >> > > The plan, as I understand

What is the correct way of reflecting make variables in moz.build?

We have a lot of places where we do things such as: CFLAGS += $(TK_CFLAGS) LOCAL_INCLUDES += $(DIST)/include/foo etc. What is the correct way of porting such variables to moz.build? Thanks! -- Ehsan ___ dev-builds mailing lis

Fwd: CFLAGS in moz.build

I just realized that we fell off dev-builds last night. I posted a patch to bug 973649 to make it possible to use CFLAGS, CXXFLAGS and LDFLAGS in moz.build. Cheers, -- Ehsan <http://ehsanakhgari.org/> -- Forwarded message -- From: Ehsan Akhgari Date: Sun, Feb 16, 2014 at

CFLAGS in moz.build

What is the plan for porting CFLAGS and friends to moz.build? Is there any work in progress for that? How can one help? Thanks, -- Ehsan ___ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listi