similar to: XCode project

Problems building celt-0.5.2 for blackfin. Use the following to configure: #!/bin/sh # bfinconf # Set up configuration to cross compile on blackfin ./configure \ --host=bfin \ --enable-fixed-point \ CC=bfin-uclinux-gcc \ CFLAGS='-O2 '\ '-mfast-fp '\ '-ffast-math '\ '-Wall -Dlinux '\ '-D__linux__ '\ '-fno-strict-aliasing '\

I?m trying to build Opus (git master) for iOS, and it doesn?t build unless I disable the ARM assembly. It looks like the problem is that Apple?s assembler doesn?t support all the assembler directives that the GNU assembler does. I suspect this is a combination of the fact that Apple platforms are Mach-O rather than Elf, and just the fact that Apple?s assembler is extremely divergent from the

Hi All, If anyone is interested, I just checked in a simple Xcode 2.1 project file in to CVS. The "build" button just runs the LLVM makefiles, but it enables some of the project/code browsing capabilities of Xcode. If you're interested, give it a whirl. The project file is in the llvm/Xcode directory. -Chris -- http://nondot.org/sabre/ http://llvm.org/

On 01/11/2011 16:16, Rob Nikander wrote: > I just downloaded and compiled LLVM and I'd like to use the JIT API in > a project that I've got in Xcode. I'm confused because I thought I > could use LLVM like a library, but it seems I can't simply include > some headers and link to lib, as usual. Or can I? I don't see a > framework or dylib file, which I would

Hi all, I just downloaded and compiled LLVM and I'd like to use the JIT API in a project that I've got in Xcode.  I'm confused because I thought I could use LLVM like a library, but it seems I can't simply include some headers and link to lib, as usual. Or can I? I don't see a framework or dylib file, which I would usually add to my Xcode project. The /usr/local/lib

On Feb 28, 2011, at 8:07 PM, Félix Cloutier wrote: > I'm using Xcode 3 to program with LLVM and Clang (both about yesterday's latest revisions), and when I compile, I get 1501 link-time warnings. All those I read were about symbol visibility. Here's an example: > > ld: warning: namespace::class::method() has different visibility (default) in

Hi Please tell me how can I use parts of WINE / WineLib (mainly Kernel32 library implementation) in Mac OS XCode projects? I tried to link kernel32.lib.so with a test application, which used one of the Kernel32 functions - GetCurrentDirectoryA(), but got a linker error, which was not able to resolve this function :? The most puzzling thing is that if I run otool on Kernel32.lib.so, it says the

I'm using Xcode 3 to program with LLVM and Clang (both about yesterday's latest revisions), and when I compile, I get 1501 link-time warnings. All those I read were about symbol visibility. Here's an example: ld: warning: namespace::class::method() has different visibility (default) in /usr/local/lib/libclangCodeGen.a(CodeGenAction.o) and (hidden) in

Hi, I'm having a hard time linking the LLVM/clang libraries in Xcode. I've been fighting this for a couple of days now, and decided to make a fresh checkout and a super-simple demo project to try and isolate the problem, but even so I'm getting undefined symbol errors in the linker for the static libraries LLVM is producing. This is really baffling, so probably I'm

Hello, I've sent this question to flac-dev not realizing that QT development belongs in ogg-dev. As it pertains more to the QT component than to the FLAC project itself, I thought I'd repeat the question here in hopes of some kind of suggestions or pointers. I'm basically attempting to compile the Xiph QuickTime component project, which fails to build. Its dependencies compile fine,

--- 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

Hello opus-dev, Can we please have review on RFCv2? We have quite a few optimizations (Eg: ifft/mdct_backwards, fixed point fft/ifft mdct_forward/backward etc) that are in my pipeline that depend on this patch series being accepted. Regards, Vish On 4 February 2015 at 12:21, Viswanath Puttagunta <viswanath.puttagunta at linaro.org> wrote: > Changes from RFC PATCH v1: > - passing

I too would like to know the status of the opus IP holders. From what I've seen on the CELT and opus lists, it seems that the CELT part of opus is covered by patents from Xiph and Broadcom, and the SILK part of opus is covered by the rest. All of the IP holders except Qualcomm and Huawei have released their patents to the public as far as opus is concerned, and the general consensus from

Thanks to Jean-Marc and Tim explaining 'git rebase -i' to me, I've factored my reorganization of the Opus Intrinsics configury into a number of hopefully more comprehensible (and thus more reviewable) pieces. This applies to the current tip of Opus Master in git. Viswanath's Ne10 changes require some slight modification to apply on top of these patches, but nothing major.

Hi, On Sat, Jan 28, 2017 at 2:04 AM, Raghavan, Karthik < karthikr at qti.qualcomm.com> wrote: > Hi > > > > I am not sure if this issue has been resolved, but on the latest opus > 1.1.4, > > · I downloaded the tarball, > > · ran ./configure followed by > > · make and then > > · make check > > > > Can you

Hi, Seems like it's not linking with libm. I suspect it has to do with linking statically with libopus.a (is that intended?). Maybe opus-tools relies on the fact that libopus is linked with libm and doesn't explicitly add it? Greg? Jean-Marc On 09/24/2013 06:09 AM, bat guano wrote: > Hi > I'm having a problem compiling opus-tools-0.1.7. > Version opus-tools-0.1.6 seems to

The patch prevents KEIL MDK compile warnings, like:   warning:  #1035-d: single-precision operand implicitly converted to double-precision Actually ARM Cortex-M4F has only a *single precision* (float) FPU. It's suit for all platforms. See the comment at the begin of patch file. Sincerely Forrest Zhang -------------- next part -------------- Specify the floating point constant with single

Ian Davidson Software Developer Clear-Com, a Vitec Group brand 7400 Beach Drive IQ Cambridge Cambridge CB25 9TP United Kingdom TEL: +44(0) 1223 815000 DDI: +44(0) 1223 815977 Fax: +44(0) 1223 815001 ian.davidson at vitecgroup.com www.clearcom.com <outbind://6-00000000D7A71728D49A6F42A4D030A8BDCE2F0D070003A2EBDA91A95F4

On 26/11/15 16:40, Jean-Marc Valin wrote: > Please report any issue you find in this release. Using the new SS4.1 code I see a 30% performance increase in my 7 years old AMD laptop. I compile with this: ./configure --disable-static --enable-intrinsics \ --enable-float-approx "make test" runs fine. Great. When I try to do the same on a server running Ubuntu

I saw the custom API, but nothing explicitly says "CELT-only" just "custom sample rate and frame size". I'll dig further now that you've pointed me in a direction. Thanks, -a On 7/6/15, 6:18 PM, Jean-Marc Valin wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > I believe what you want is called Opus custom (OPUS_CUSTOM in the > code).