Gregory Hainaut dd5868f9ba Also remove file of 3rdparty		2015-06-04 08:56:19 +02:00
..
Common.props	Yet another missing .props ... ;_;	2010-04-14 20:02:36 +00:00
ProjectRootDir.props	Made a special .props file for null plugins, since they seem to have a different folder structure than the rest.	2010-04-14 19:57:33 +00:00
wx_adv_vs2012.vcxproj	Change the vs2012 project files to use the v110_xp platform toolset, and the vs2013 project files to use the v120_xp platform toolset, so that the resulting executables can be run in Windows XP/2003.	2014-01-24 15:30:34 +00:00
wx_adv_vs2012.vcxproj.filters	Because vs2012==vs11 and vs2013==vs12, which is extremely confusing, I renamed the project files to use the full year as the name.	2013-11-27 16:53:36 +00:00
wx_adv_vs2013.vcxproj	Change the vs2012 project files to use the v110_xp platform toolset, and the vs2013 project files to use the v120_xp platform toolset, so that the resulting executables can be run in Windows XP/2003.	2014-01-24 15:30:34 +00:00
wx_adv_vs2013.vcxproj.filters	Because vs2012==vs11 and vs2013==vs12, which is extremely confusing, I renamed the project files to use the full year as the name.	2013-11-27 16:53:36 +00:00
wx_base_vs2012.vcxproj	Change the vs2012 project files to use the v110_xp platform toolset, and the vs2013 project files to use the v120_xp platform toolset, so that the resulting executables can be run in Windows XP/2003.	2014-01-24 15:30:34 +00:00
wx_base_vs2012.vcxproj.filters	Because vs2012==vs11 and vs2013==vs12, which is extremely confusing, I renamed the project files to use the full year as the name.	2013-11-27 16:53:36 +00:00
wx_base_vs2013.vcxproj	Change the vs2012 project files to use the v110_xp platform toolset, and the vs2013 project files to use the v120_xp platform toolset, so that the resulting executables can be run in Windows XP/2003.	2014-01-24 15:30:34 +00:00
wx_base_vs2013.vcxproj.filters	Because vs2012==vs11 and vs2013==vs12, which is extremely confusing, I renamed the project files to use the full year as the name.	2013-11-27 16:53:36 +00:00
wx_config_vs2012.vcxproj	Change the vs2012 project files to use the v110_xp platform toolset, and the vs2013 project files to use the v120_xp platform toolset, so that the resulting executables can be run in Windows XP/2003.	2014-01-24 15:30:34 +00:00
wx_config_vs2012.vcxproj.filters	Because vs2012==vs11 and vs2013==vs12, which is extremely confusing, I renamed the project files to use the full year as the name.	2013-11-27 16:53:36 +00:00
wx_config_vs2013.vcxproj	Change the vs2012 project files to use the v110_xp platform toolset, and the vs2013 project files to use the v120_xp platform toolset, so that the resulting executables can be run in Windows XP/2003.	2014-01-24 15:30:34 +00:00
wx_config_vs2013.vcxproj.filters	Because vs2012==vs11 and vs2013==vs12, which is extremely confusing, I renamed the project files to use the full year as the name.	2013-11-27 16:53:36 +00:00
wx_core_vs2012.vcxproj	Change the vs2012 project files to use the v110_xp platform toolset, and the vs2013 project files to use the v120_xp platform toolset, so that the resulting executables can be run in Windows XP/2003.	2014-01-24 15:30:34 +00:00
wx_core_vs2012.vcxproj.filters	Because vs2012==vs11 and vs2013==vs12, which is extremely confusing, I renamed the project files to use the full year as the name.	2013-11-27 16:53:36 +00:00
wx_core_vs2013.vcxproj	Change the vs2012 project files to use the v110_xp platform toolset, and the vs2013 project files to use the v120_xp platform toolset, so that the resulting executables can be run in Windows XP/2003.	2014-01-24 15:30:34 +00:00
wx_core_vs2013.vcxproj.filters	Because vs2012==vs11 and vs2013==vs12, which is extremely confusing, I renamed the project files to use the full year as the name.	2013-11-27 16:53:36 +00:00