On Thu, Dec 6, 2018 at 6:10 PM Gijs Kruitbosch wrote:
> Can someone elaborate on what this means for debugging on Windows, and
> for our onboarding story on Windows?
At least in terms of stepping through, examining variables, etc.,
clang-cl is on par with MSVC. If there are specific, stop-the-pr
Can someone elaborate on what this means for debugging on Windows, and
for our onboarding story on Windows?
I don't do this very often, but I ran into this today and the story is
already very poor. I'm currently trying to work out why a patch I have
crashes on startup. I tried using google, an
On Thu, Dec 06, 2018 at 03:34:59PM -0500, Jonathan Kew wrote:
While I sympathize with the concern that "supporting more than one
compiler is a maintenance burden", this still leaves me feeling a
little uneasy. Ensuring that our code builds successfully with
multiple compilers is a useful way to
On 06/12/2018 15:00, Ted Mielczarek wrote:
Hello,
In light of the fact that we've switched to clang-cl for our Windows builds[1],
we are planning to drop support for compiling Firefox with MSVC in the near
future[2]. Our estimate is that this will happen sometime in Q1. Supporting
more than o
\o/
On Thu, Dec 06, 2018 at 03:00:12PM -0500, Ted Mielczarek wrote:
Hello,
In light of the fact that we've switched to clang-cl for our Windows builds[1],
we are planning to drop support for compiling Firefox with MSVC in the near
future[2]. Our estimate is that this will happen sometime in Q
Hello,
In light of the fact that we've switched to clang-cl for our Windows builds[1],
we are planning to drop support for compiling Firefox with MSVC in the near
future[2]. Our estimate is that this will happen sometime in Q1. Supporting
more than one compiler is a maintenance burden and we've
6 matches
Mail list logo
