i've downloaded source code from 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?
I've created new visual studio 2005 project and copied all settings, it works!
Related
I know visual C++ 2015-2022 is installed because:
A. I see it in Apps & Features (Microsoft Visual C++ 2015-2022 Redistributable (x64) - 14.31.31103
B. I see it in registry HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\14.0\VC\Runtimes\X64
but %VCINSTALLDIR% is not set on my path, and I cant find the dll's anywhere.
I need to be really specific with my IT dept to get this fixed. I want to add the dll to the system path but I have to find them first!
I managed to find VC_redist.x64.exe in C:\ProgramData\Package Cache\{2aaf1df0-eb13-4099-9992-962bb4e596d1} but I think that is pretty strange... it may be unrelated to the install.
Any help appreciated!
For me they are at
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Redist\MSVC
Do note that %VCINSTALLDIR% only works in the Visual Studio Developer Command Prompt. That should be located under the Visual Studio XXXX folder in your start menu or it can be launched directly from inside visual studio. You can then enter
cd %VCINSTALLDIR%
in the terminal to get where the directory is located on your machine.
According to Github/Microsoft Visual C++ Files are in %VCINSTALLDIR%Redist\MSVC\v143 folder.
The easiest way to locate the redistributable files is by using environment variables set in a developer command prompt. In Visual Studio 2022, the redistributable files are in the %VCINSTALLDIR%Redist\MSVC\v143 folder. In the latest version of Visual Studio 2019, you'll find the redistributable files in the %VCINSTALLDIR%Redist\MSVC\v142 folder. In both Visual Studio 2017 and Visual Studio 2019, they're also found in %VCToolsRedistDir%. In Visual Studio 2015, these files can be found in %VCINSTALLDIR%redist<locale>, where is the locale of the redistributable packages.
I know visual C++ 2015-2022 is installed because:
A. I see it in Apps & Features (Microsoft Visual C++ 2015-2022
Redistributable (x64) - 14.31.31103
...
You're confusing Visual Studio (the development environment) with Microsoft Visual C++ Redistributable (a runtime support library). There isn't even such a thing as "visual C++ 2015-2022". Each version of Visual Studio has one specific year, such as Visual Studio 2017 (VS2017). The redistributable works for all Visual Studio versions between VS2015 and VS2022.
%VCINSTALLDIR% is set by the command prompts of all Visual Studio version, but the value will differ between Visual Studio variants. You can install multiple versions of Visual Studio side by side on the same computer.
I migrate Visual Studio 2013 project to visual studio 2019 and recompiler my all dlls and other files using visual studio 2019. But when I run my application, it still requires msvcr120d.dll in release mode.
Anyone help me out to fix this.
Go to settings and select proper Platform Toolset
for vs2019 select v142
By default Python 3.3 installers are built with Visual studio 2010.
I have visual studio 2013 and I want to generate the python33.dll from visual studio 2013.
When i link my application with dll generated from visual studio 2013 then it is getting crash in "Py_Initialize" function but when i link my application with dll generated from visual studio 2010 then everything works fine.
I have tried to build from source with VS2013. Going into "PCBuild" folder and try to build Python33.dll from .sln file but application is getting crashed.
How to make application run without crash with visual studio 2013 dll ?
Is there any steps to compile the Python source code in MinGW in windows ?
Thanks in Advance
I have C++ VS2008 project and my lovely IDE VS13. How can I work into VS13, but compile and debug project like in would be VS08. When I open VS2008 *.sln files that wrote to me about one-way upgrade, and how you i guess you understand, project after open in vs2013 don't open in vs2008.
For now, I use VS13 like notepad then copy all files text to alt+tab opening VS 2008 IDE and there are run project. And again work in VS13.
Based on Microsoft product lifecycle policies,
https://support.microsoft.com/en-us/lifecycle/search?sort=PN&alpha=Visual%20Studio&wa=wsignin1.0
Visual Studio 2008's mainstream support ended in April 2013, while Visual Studio 2013 was released in Jan 2014. That means Visual Studio 2013 will not support Visual Studio 2008 bits, so not a surprise if native multi targeting does not show v80.
I don't think you can easily get side by side, as VS2008 is too old, and its C++ project is not even MSBuild script. Once converted to VS2013, there is no way back.
Why cannot you just let VS2008 go? I guess that's why you get so many down votes.
You can't convert the solution to Visual Studio 2013 and still open it in Visual Studio 2008. You can, however, tell Visual Studio 2013 to use the Visual Studio 2008 compiler.
To do that, convert your solution to Visual Studio 2013 (don't forget to keep a copy of the original file, just in case), then open the project properties, go to the General options and select the Visual Studio 2008 platform toolset.
Yesterday I had to reinstall Visual Studio 2010 on a computer with both VS 2012 and VS 2013, because I needed to compile older code. The Visual Studio 2010 installation caused header file issues, as described here . I followed the details provided in the answers, and got VS 2010 to install properly.
Now, when I run the VS 2010 version of msbuild, it compiles C++ code flawlessly. All the header files are properly installed in c:\program files (x86)\Microsoft Visual Studio 10.0\VC\include .
However, when I open a project in Visual Studio 2013, and set the Platform Toolset to v100 (which is VS 2010), it can't find the header files! Although they are right there!
This was originally a VS 2013 project, and I changed the platform toolset to VS 2010. This did not change the Include Directories property of the project, which was $(VC_IncludePath).
This macro is not defined by VS 2010, so the compiler can't find the include files.