warning MSB8012 - Building a Visual Studio 2003 project on Visual studio 2015
I'm trying to build a Visual Studio 2003 project (SimpleIni) on Visual studio 2015.
After opening the project it provided me an option to Auto upgrade it. However after upgrading I'm unable to Build the solution and getting following warnings:
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppBuild.targets(1189,5): warning MSB8012: TargetPath(E:\abc\VisualStudioCpp\test\simpleini-master\Debug Unicode\SimpleIni.exe) does not match the Linker's OutputFile property value (E:\abc\VisualStudioCpp\test\simpleini-master\Debug Unicode\testsi.exe). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile).
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppBuild.targets(1191,5): warning MSB8012: TargetName(SimpleIni) does not match the Linker's OutputFile property value (testsi). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile).
1>ConvertUTF.obj : warning LNK4075: ignoring '/EDITANDCONTINUE' due to '/SAFESEH' specification
I have gone through the following links:
How do I fix warning MSB8012 in a static library project in Visual C++ 2010?
However I'm not able to find how to change Linker settings on Visual Studio 2015.
Can someone tell me how to build a Visual Studio 2003 project on Visual studio 2015?
To fix the problem you should change the options for you project as follows:
General tab -> Target Name = SimpleIni, Target Extension = .exe
Also on General tab check that application type of your project is Application.
All of these options marked on the attached screenshot:
Linker tab -> All parameters -> Output file -> $(OutDir)$(TargetName)$(TargetExt)
This option is marked on the screenshot bellow:
- How portable is code with #pragma optimize?
- Make warn_unused_result applied to all function with GCC
- Multiple threads and CPU cache
- Linking error vs. compilation error
- how to compile multiple instances of a source file linking to it different files.o
- Background compile in VS2010 and C/C++
- What Turing complete macro languages are available for C/C++
- How to use Cython to compile Python 3 into C
- Are forward declarations needed when the typedef declaration is done?
- How to assign real and imaginary parts of complex variables in C
- Strict aliasing between Complex numbers and real numbers in C
- How to CORRECTLY install gsl library in Linux?
- Using = operator on atomic variable?
- Unknown conversion types in this program I'm meant to compile
- Iterator in C language
- Treating __func__ as a string literal instead of a predefined identifier
- c - strcpy with struct string returning error
- Segmentation fault when executing a Python script in a C program?
- Questions about C Function Prototypes and Compilation
- What is the purpose of "-Wa,option" in GCC?
- Do we have c99 subflags
- netcat gcc compile option so that IDA pro can show function name
- What is the correct way to free output buffer after call to openssl::i2d_X509?
- How can I link C++ files to a C program?
- Why doesn't this program in C compile? Error: undefined reference to `i2c_smbus_read_byte_data'
- integer promotion isn't taken into account
- Why do I get a SEGFAULT when I try to sort an array of integers using K & R code examples?
- Are C preprocessor statements a part of the C language?
- FFMPEG Api conversion from YUV420P to RGB produces strange output
- Why is the tree constructed this way incorrect?