On 08/05/2015 00:05, Dann Corbit wrote: > After building the debug version of the x64 projects, I get linker errors. > I have to do a project clean, and then I can debug. > But then I get linker errors with the release version of the project: > 46>------ Rebuild All started: Project: mpf.get_si, Configuration: Release > x64 ------ > 38> ERROR Last MPIR build was \x64\Debug, not lib\x64\Release > 40> ERROR Last MPIR build was \x64\Debug, not lib\x64\Release > 40>C:\Program Files > (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(122,5): > error MSB3073: The command "..\check_config x64 Release > 40>C:\Program Files > (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(122,5): > error MSB3073: :VCEnd" exited with code 1. > 47>------ Rebuild All started: Project: mpf.get_ui, Configuration: Release > x64 ------ > 38>C:\Program Files > (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(122,5): > error MSB3073: The command "..\check_config x64 Release > 38>C:\Program Files > (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(122,5): > error MSB3073: :VCEnd" exited with code 1. > 39> ERROR Last MPIR build was \x64\Debug, not lib\x64\Release > 39>C:\Program Files > (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(122,5): > error MSB3073: The command "..\check_config x64 Release > 39>C:\Program Files > (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(122,5): > error MSB3073: :VCEnd" exited with code 1. > 9> ERROR Last MPIR build was \x64\Debug, not lib\x64\Release > 9>C:\Program Files > (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(122,5): > error MSB3073: The command "..\check_config x64 Release > 9>C:\Program Files > (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(122,5): > error MSB3073: :VCEnd" exited with code 1. > > Everything is in separate folders (even the header files). > Why is this strangeness necessary? > I have never seen any other software behave this way.
The tests have to be set up to pick up one specific configuration and it is (in my view at least) sensible to assume that the user wants to test the version that was the last one that they built. The design is hence based on this method of working: 1. Build a specific configuration 2. Test _this_ configuration 3 Repeat for other configurations if needed But it is easy to build multiple configurations and then edit output_params.bat to test a specific configuration - this is explained in the readme.txt file. Brian -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to mpir-devel+unsubscr...@googlegroups.com. To post to this group, send email to mpir-devel@googlegroups.com. Visit this group at http://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
