similar to: build opus codec with visual studio 2005

i've downloaded source code from <http://www.opus-codec.org/downloads/> http://www.opus-codec.org/downloads/ but in the tarball there is only one project for visual studio 2010, it builds well but if i use .lib on visual studio 2005 they won't work... Anyone knows how to compile with visual studio 2005? -------------- next part -------------- An HTML attachment was scrubbed...

Hi everone, I currently try to test the Opus codec. It seems, however, that it is more easy to do that in Linux. Nevertheless, I have compiled the sources in Visual Studio 2010. Here are some hints: 1) "static inline int function(...)" (combination of static and inline) does not work with Visual Studio 2010. I defined a macro which translates all "inline" to nothing. 2) I

On 2013-10-29 2:39 PM, Akshit Jain wrote: > Thanks a lot for replying. This is the output > >>------ Build started: Project: celt, Configuration: Debug Win32 ------ > 1> fatal: No names found, cannot describe anything. > 1> The system cannot find the file C:\Users\user\Desktop\mUOn\Audio. > 1> #define OPUS_VERSION ""=">

I am using mvs 2012 but the .sln provided is of msv 2010 so on opening .sln it tries to update libraries which is successful but I am unable to build (compile) it as it gives series of errors. I am pretty new to these things so can anyone tell me if I am doing anything wrong or how to create(.lib and .dll) files so I can use them in my project. Please forgive me if I have asked something foolish.

Hi Opus-ers! Could someone with a Windows machine and Microsoft Visual Studio 2015 check the attached patch for me? You can get the free Community Edition (license says we're allowed to use it because we're working on open-source stuff). Let me know if problems/questions :-) Orestes -------------- next part -------------- A non-text attachment was scrubbed... Name:

1. If you're building in CCS, I hope you have created new projects and imported the source and header files. 2. Then right click on project you want to build -> Build Properties -> Under C600 Compiler, click on Basic Options -> Change Optimization level On Fri, Sep 6, 2013 at 12:30 AM, <opus-request at xiph.org> wrote: > Send opus mailing list submissions to >

Hi Marcus, There seems to be a conflict between the autotools-created config.h.in and the same file added by your patch. Any way you can use use a different name? Cheers, Jean-Marc On 04/02/2019 01:39 AM, Marcus Asteborg wrote: > Hi, > > > Here is a proposal for adding CMake in addition of Autotools. > > > See the attached patch for changes or the pull request here:

Hi, Here is a proposal for adding CMake in addition of Autotools. See attached patch for changes or the pull request here: https://github.com/xiph/opus/pull/100 The CMake scripts are parsing the filelist from Autotools, so only one file list needs to be maintained. With this change the checked in Visual Studio solution can be removed and no longer need to be maintained and updated when

I'd like to add support for CELT in a C# application. To do so, I'd like to build CELT as a static library using VS which I would then wrap with C++/CLI so I can access the encode/decode funtionality from within C#. Is it possible to compile CELT using Visual Studio? The first issue I ran into was that VS doesn't support the 'restrict' keyword. It does have __restrict which

Hi, Just to clear things up... So 1.1 has some new analysis code that increases the amount of CPU. When building as floating point (which you appear to be doing, right?), the new code is enabled at complexity 7 and up (opusenc defaults to complexity 10 IIRC). This is why you've been seeing an increase in the CPU time. In version 1.0.x, complexity 5-10 are the exactly the same for music.

Thanks, it applies now. I think you'd also want to add some (all?) of these files to EXTRA_DIST in Makefile.am, otherwise your cmake files won't be included in release tarballs, which are generate using "make dist". To test, you should try running run "make dist" to generate a tarball yourself. From there, you try building the contents with your cmake files and see if

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html><head><title></title> <META http-equiv=Content-Type content="text/html; charset=windows-1251"> <meta http-equiv="Content-Style-Type" content="text/css"> <style type="text/css"><!-- body { margin: 5px 5px 5px 5px;

I am working on a project that transports audio in realtime from a linux box to a windows box throuh libcelt. The windows client program is written in C# and C++ and I therefore need the celt library in its most recent version (0.7) to be able to compile in Visual Studio 2008. In order to do this I, as I understand it, need a .vcproj file for the project. Are there any plans on making such a

Hi, It looks like cmake currently defaults to no optimization, which I think is a bit unexpected for most users. I don't know how to do that in cmake, but it would be good to default to a "release" build with optimizations. Can you have a patch to do that? Also, is there a way to manually add flags to the compiler (like setting CFLAGS with autotools)? Cheers, Jean-Marc On

Hi, Here is a proposal for adding CMake in addition of Autotools. See the attached patch for changes or the pull request here: https://github.com/xiph/opus/pull/100 The CMake scripts are parsing the filelist from Autotools, so only one file list needs to be maintained. With this change the checked in Visual Studio solution can be removed and no longer need to be maintained and updated when

Is this a common warning? The decoder doesn't return an error on it, but I see it a lot in my test application on windows. It is non existent on my linux box. I haven't tried mingw yet. please note that I'm using visual studio 2008 w/the vcproj that Bjoern Rasmussen made for 0.5.2 (w/some file references removed) at the moment and it is giving a lot of C4554 warnings

Hi all: How do I create opus encoder and decoder executable on Windows using MS Visual Studio 2010? What I'm doing is the following: 1. I downloaded the codebase on my local drive using: $ git clone git://git.opus-codec.org/opus.git 2. Then I go to D:\opus\win32\VS2010 and open the opus.sln using MS Visual Studio 2010. 3. Then I build the solution opus. I get 3 executable at

Hi Mark, Thanks for the feedback. By default CMake is building the static library in debug, to get other things one has to explicit turn it on. To build in release mode for CMake you use the following flag: -DCMAKE_BUILD_TYPE=Release https://cmake.org/cmake/help/latest/variable/CMAKE_BUILD_TYPE.html CMAKE_BUILD_TYPE — CMake 3.14.1

Hi On the opus-codec web page here ---> http://www.opus-codec.org/development/ Underneath "Source code repository" there are options to download the gits. As well as the traditional "$ git clone git://git.opus-codec.org/opus.git" there are also Snapshots. opus-master.tar.gz opus-1.0.x-branch.tar.gz It's a great idea... To download HEAD the command can be like this...

Hi Max, cmake .. -G "Visual Studio 16 2019" -A ARM64 -DBUILD_SHARED_LIBS=ON -DBUILD_TESTING=ON cmake --build . -j 10 Is building for me, but I don't have any Windows Arm64 device so cannot test it. Note that: Neon will not work on windows out of the box builds due renamed header: