version_vs100.vcxproj doesn't set PlatformToolset, so it defaults to v100 (I think).
opendune_vs100.vcxproj sets PlatformToolset to v110_xp
version project doesn't build anything so there's no need to specify the platform toolset. For opendune project it's different as MSVC2012 by default uses MSVC2010 toolset when it loads a v100 project. And in this case it requires MSVC2010 to be installed. That's why I made it use v110_xp if the project is opened with MSVC2012.
VC is still asking me to update the toolset when I open the project, hence
That's strange because there's no platform toolset option for Makefile type projects
I know, but VC still asks me to upgrade:
------ Update VC++ projects started -------
Updating project 'opendune'...
No update required.
Updating project 'version'...
Configuration 'Debug|Win32': changing Platform Toolset to 'v110' (was
I still don't understand why VC even tries to upgrade. VC2012 can open VC2010 projects without upgrading, they use the same format.
But there's no possibility to even set it using the properties GUI. Makefile type projects don't have a platform toolset setting. So I don't understand why your VC complains about it.
I don't understand either.
Does yours not complain?
If so, you must have a better VC then me. :p
There are no complains from my VC, that's why I don't understand why yours complains. And as I already said, it's not possible to set a platform toolset for Makefile type projects as per definition they don't need it.
What VC are you running?
Would it hurt to set it anyway?
I use VS Express 2012 for Windows Desktop, but TrueBrain uses the full VS2012 version without complains either. And as I already said, there's no way to set it via the GUI so I don't see why it should be set in the project file.
I think we can close this issue, as it is not even preventing to compile anything.
-Fix(#209): Fix compilation under MSVC++ express 2010
remove Platformtoolset so the default one is picked
@glx22 : does my fix work for your VS Express 2012 ? (I have tested with VS Express 2010)
@OlafvdSpek : which Visual Studio version are you using ?
I'm currently running 2013 and 2015.
For me it works, it uses the platform toolset I set via environment variable PlatformToolset (Windows7.1SDK to be precise). Tested with express 2010, express 2012 and community 2015.
@OlafvdSpek : does my fix work well for you with 2013 and 2015 ?
I think the 'fix' is right but I don't know how to test it.
I also noticed VC add a space before the closing />, the Git files are missing this space.
@OlafvdSpek : It is OK if the project build with your Visual Studio(s)
Without the space before /> it is still correct XML and VC has no problem reading the files
-Fix: add space before XML /> in VS2010 project files
see issue #209
it will be consistent with Visual Studio 2010 behaviour
@OlafvdSpek : is the last patch ok for you ? :)
-Fix: add space before XML /> in VS2010 project file (continued)
ImageHasSafeExceptionHandlers element has been forgotten in
see issue #209