Displaying 5 results from an estimated 5 matches similar to: "[PATCH 1/3] appveyor: include opus.dll and opus.exp files if available"
2016 Jul 15
3
[PATCH 1/4] Create a simple project to create version.h to run before any other
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 ++++++++++++++++-
2004 Dec 03
2
[LLVMdev] [Fwd: Updated LLVM Visual Studio project files]
Could someone please apply this patch to the Win32 support so that
Morten and Jeff can handle the recent changes? I can't do it because
I"m on the road with only email access.
Thanks,
Reid.
-----Forwarded Message-----
> From: Morten Ofstad <morten at hue.no>
> To: Reid Spencer <reid at x10sys.com>
> Subject: Updated LLVM Visual Studio project files
> Date: Thu,
2015 Mar 02
13
Patch cleaning up Opus x86 intrinsics configury
The attached patch cleans up Opus's x86 intrinsics configury.
It:
* Makes ?enable-intrinsics work with clang and other non-GCC compilers
* Enables RTCD for the floating-point-mode SSE code in Celt.
* Disables use of RTCD in cases where the compiler targets an instruction set by default.
* Enables the SSE4.1 Silk optimizations that apply to the common parts of Silk when Opus is built in
2004 Dec 03
0
[LLVMdev] [Fwd: Updated LLVM Visual Studio project files]
On Fri, 3 Dec 2004, Reid Spencer wrote:
> Could someone please apply this patch to the Win32 support so that
> Morten and Jeff can handle the recent changes? I can't do it because
> I"m on the road with only email access.
I'd be happy to do it. Can someone send me the patch as an attachment
off-list?
-Chris
> > <Tool
> >
2008 May 21
3
[LLVMdev] 2.3 Pre-release available for testing
Razvan Aciu wrote:
> As I saw from the mailing list the MSVC 2005 patches were made to take into
> account the new files from the development branch, files which are not in
> the 2.3 release. So for now the below patch is the only one functional for
> the release. If I am wrong, please someone correct me.
>
> If someone can make a 2005 patch for the release branch, it is ok.