similar to: Retiring VS2015 Support

--- win32/VS2015/opus.vcxproj | 2 ++ win32/VS2015/opus.vcxproj.filters | 6 ++++++ 2 files changed, 8 insertions(+) diff --git a/win32/VS2015/opus.vcxproj b/win32/VS2015/opus.vcxproj index d9aaa03..f55ea37 100644 --- a/win32/VS2015/opus.vcxproj +++ b/win32/VS2015/opus.vcxproj @@ -852,6 +852,7 @@ <ClInclude Include="..\..\celt\vq.h" /> <ClInclude

Not 100% if this is an LLVM question or a CLang question, though I expect LLVM. On Linux, if I pass '-fsave-optimization-record' to 'clang', then it produces a '*.opt.yaml' file. However, the same thing run on Windows using 'clang' built with VS2015 silently ignores this option. Is this a bug or is it intentional? And if it is intentional, how can I configure

Avoids trying to create and replace version.h more than once which led to file-locking errors with multicore builds. --- Makefile.am | 1 + win32/VS2015/celt.vcxproj | 48 +++++++++++++++++--------- win32/VS2015/generate_version.vcxproj | 65 +++++++++++++++++++++++++++++++++++ win32/VS2015/opus.sln | 32 ++++++++++++++++-

Using -i should prevent failing if the files don't exist. --- appveyor.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appveyor.yml b/appveyor.yml index c85b0b1..ad9c6c0 100644 --- a/appveyor.yml +++ b/appveyor.yml @@ -17,7 +17,7 @@ build: verbosity: minimal after_build: -- cmd: 7z a opus.zip win32\VS2015\%PLATFORM%\%CONFIGURATION%\opus.lib include\*.h +- cmd: 7z

Orestes Zoupanos wrote: > VS2015, considering it's quite recent and the Community Edition has a > free-to-use-for-open-source license going on. > >>> Yup, into win32\VS2010 and VS2015. >> >> VS2015 or VS2005? Currently FLAC has 2 Visual Studio solutions: one >> for VS2005 >> (and 2008) and another for VS2010 and all newer (2012, 2013, 2015...)

At Microsoft, we believe that we gain a competitive advantage by making the Visual Studio versioning story as complicated as possible. To wit: The compiler in the first VS 2015 release was version 19.00. For each update/hotfix release, we bumped that version by .01. When VS 2017 was released, we decided to keep the major compiler version the same to signify backwards-binary-compatibility with the

Hi all, Firstly sorry I'm a bit late responding on this one. Internally to ARM we build LLVM for Windows. Our current build cluster has only VS2013 installed and as a result of this thread we've been working on getting VS2015 installed. This involves a certain amount of IT-wrangling as the cluster we use is company-wide. There have been some hiccups regarding licensing of MSVC

There are certainly enough people making commits that work with VS2015 but not VS2013 that the "would it be useful" question is pretty well answered. I've already brought up the idea on my team, as it's obviously coming and we need time to coordinate with internal consumers of the toolchain. --paulr From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Zachary

Apart from the obvious licencing issues, each time I have moved from one version of VC++ to another, the big problem I have had is not specifically the ABI at the register passing, stack organisation level, but rather the implementation details of the Standard C++ libraries, and in particular the STL containers. While the compiler team puts considerable effort into maintaining the ABI, the C++

> -----Original Message----- > From: aaron.ballman at gmail.com [mailto:aaron.ballman at gmail.com] On Behalf > Of Aaron Ballman > Sent: Friday, July 29, 2016 2:19 PM > To: Zachary Turner > Cc: Sean Silva; Robinson, Paul; Piotr Padlewski; llvm-dev at lists.llvm.org > Subject: Re: [llvm-dev] Upgrading to MSVC 2015 > > There are not that many people making commits to

FWIW, no objections from me, after all I proposed this 3 months ago :) Probably Aaron Ballman should comment though since the primary objection last time was his. On Fri, Jul 29, 2016 at 2:00 PM Sean Silva <chisophugis at gmail.com> wrote: > On Fri, Jul 29, 2016 at 1:23 PM, Robinson, Paul via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> There are certainly

There are not that many people making commits to working around MSVC 2013 as I think are claimed (there are certainly a lot of commits for working around MSVC in general, however). A quick search through the code base shows there are 8 instances where we've worked around MSVC 2013 issues (there may be more that someone worked around in an ad hoc manner and did not mark). We definitely had *a

On Fri, Jul 29, 2016 at 1:23 PM, Robinson, Paul via llvm-dev < llvm-dev at lists.llvm.org> wrote: > There are certainly enough people making commits that work with VS2015 but > not VS2013 that the "would it be useful" question is pretty well answered. > I've already brought up the idea on my team, as it's obviously coming and > we need time to coordinate with

On Sat, Jul 30, 2016 at 1:58 PM, Robinson, Paul <paul.robinson at sony.com> wrote: > > >> -----Original Message----- >> From: aaron.ballman at gmail.com [mailto:aaron.ballman at gmail.com] On Behalf >> Of Aaron Ballman >> Sent: Friday, July 29, 2016 2:19 PM >> To: Zachary Turner >> Cc: Sean Silva; Robinson, Paul; Piotr Padlewski; llvm-dev at

Hi, As I understand it the specific issue we're seeing is related to what Martin described. But due to numerous bugs found when mixing objects compiled with different versions of MSVC in the past, we now are shy of doing it even if it seems to work superficially - that's no guarantee bugs won't be found down the line. We'd much prefer to stay within the realms of what Microsoft

> -----Original Message----- > From: aaron.ballman at gmail.com [mailto:aaron.ballman at gmail.com] On Behalf > Of Aaron Ballman > Sent: Saturday, July 30, 2016 12:41 PM > To: Robinson, Paul > Cc: Zachary Turner; Sean Silva; Piotr Padlewski; llvm-dev at lists.llvm.org > Subject: Re: [llvm-dev] Upgrading to MSVC 2015 > > On Sat, Jul 30, 2016 at 1:58 PM, Robinson, Paul

https://www.visualstudio.com/en-us/news/vs2015-vs.aspx Is it time? 2016-03-31 12:03 GMT-07:00 Aaron Ballman via llvm-dev < llvm-dev at lists.llvm.org>: > On Thu, Mar 31, 2016 at 2:57 PM, Zachary Turner <zturner at google.com> > wrote: > > > > > > On Tue, Mar 29, 2016 at 10:42 AM Aaron Ballman <aaron at aaronballman.com> > > wrote: > >>

As mentioned upthread, we're still on update 2 for various reasons. On Thu, Sep 1, 2016 at 1:07 PM, Robinson, Paul <paul.robinson at sony.com> wrote: > Hi Reid, first off thanks *very* much for all your help fixing > 2013-related problems. We really appreciate it. > > > > Let me propose a target date of September 15 for advancing the minimum MS > compiler to

Probably not. It's very confusing because they are transitioning to a new versioning scheme. The current version if Visual Studio 2015. The next version is Visual Studio 15. The link you posted was for the RTM of 2015, just over a year ago. But 15 is still in Preview. When 15 goes to RTM, then we can revisit the question of making 2015 the minimum required version. On Fri, Jul 29, 2016

Hi, A few tests seem broken for a long time, some for more than a month. Would it possible for respective owners to take a look please? I'm at checkout 133a7e631cee97965e310f0d110739217427fd3d, compiling on Windows 10. These tests fail with Visual Studio 2019: Failing Tests (7): Clang Tools :: clang-tidy/checkers/cert-mem57-cpp-cpp17.cpp Clang Tools ::