On Mon, Jul 1, 2019 at 11:00 PM Paul Schauble wrote:
> The issue of 8.3 file name is too complex to explain in an error message. I
> think the error message should be something like:
> ...
> I will write the article if requested.
We welcome improvements to our documentation and our error message
Apparently upgrading Node is the thing du jour, because Mark was just
emailing dev-builds about a more conservative upgrade (to Node 8.12)
several weeks ago. :)
AFAIK, the primary limitation is what sort of Node version support our
Linux distributions have. You can see this information for key s
On Sun, Nov 11, 2018 at 1:25 AM Victor Porof wrote:
> 1. Built this simple trace.cpp:
> https://gist.github.com/victorporof/e9809e33c4dc67ef388672791c4c80cd
> - Used `clang++ trace.cpp -mmacosx-version-min=10.9 -c -o trace.o`
> - I’m building this without `-finstrument-functions`, obviously.
>
>
Does this user have a bugzilla :alias so that folks submitting patches
via MozReview or similar can just write r=build-peer or something,
rather than having to manually select the appropriate shared queue
after submitting their patch for review?
-Nathan
On Wed, Oct 11, 2017 at 1:41 PM, Chris Coop
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-c alone is close
> to the limit, so changing tha
On Thu, Oct 27, 2016 at 7:31 PM, Chris Peterson wrote:
> The Stylo team would like to make libclang a build-time dependency so we can
> generate C++/Rust bindings as part of the local build.
What is the benefit of doing this, especially for people not working on Stylo?
-Nathan
__
On Mon, Aug 22, 2016 at 6:52 PM, Mike Hommey wrote:
> On Mon, Aug 22, 2016 at 06:33:44PM -0400, George Wright wrote:
>> it is already the default software canvas option on all platforms
>
> It's not. All Tier-1 platforms != all platforms. That's arguably the
> main problem.
What prevents it from
On Wed, Sep 16, 2015 at 11:01 AM, MichaelA wrote:
> Since the inclusion of bug 1163328 (
> https://bugzilla.mozilla.org/show_bug.cgi?id=1163328), Intel's C++
> compiler (ICL) fails to build any source files that include
> runnable_utils.h from the media transport library due to its usage of
> Tup
The way that's been discussed to fix this is to have the mozbuild frontend
figure out that if there's a file in EXPORTS, then it must either a) live
on disk, or b) be present in GENERATED_FILES, and do the right thing. If
neither a) nor b) is true, then it is a configuration error.
The GENERATED_
On Thu, Mar 12, 2015 at 5:39 AM, Chris Pearce wrote:
> Breaking VisualStudio Intellisense also broke most of the code navigation
> things that make VisualStudio awesome. I don't build with VisualStudio, I
> build with the command line because I like to build && run, and I like to
> pipe the outpu
Hi all,
When discussing the recent transition to only supporting unified builds,
some people were apparently concerned about how this would affect Visual
Studio projects (i.e. Intellisense), since the Visual Studio project files
generated via |mach build-backend| only listed the individual source
I have been poking at the build system a bit for the last couple of weeks and
feel like I am running out of ideas of things that could be (usefully) fixed.
What are some of the moderately-sized (~1-2 week-ish) things that need doing in
the build system?[1] My perception is that there are many
Bug 1042878 has landed on inbound, and changes many *_CFLAGS variables to
appear as lists to moz.build. This change enabled the easy removal of several
dozen Makefile.in's from the tree.
As a side-effect, this bug also changes the Mozilla-provided PKG_CHECK_MODULES
autoconf macro to use AC_SUB
Bug 1044162, currently on inbound only, removed JS_MODULES_PATH from the build
system. In its place, it added logic to EXTRA_JS_MODULES and
EXTRA_PP_JS_MODULES for defining their final location under
$(FINAL_TARGET)/modules/. So whereas before, a moz.build might have contained:
JS_MODULES_PAT
14 matches
Mail list logo
