I understand you want to avoid sync issues and don't expect any maintainers
will be using VS2013.
> Your second proposal is pretty much the same as the first one, but in
> disguise (instead of having 2x the vcxproj files, with half of them going
> untested, we have vcxproj files that are twice as large, with half of their
> content going untested).
To be fair, it is only the platform configurations that would be duplicated,
and the project settings stored in them rarely change once the directories and
outputs are set up. The new runtime configurations would still be editable in
VS2012, even if they can't compile some of them in VS2012. If someone is
editing the project settings, they can select multiple (e.g. Debug-2012 and
Debug-2013) so the changes are applied in both.
The scripting approach to changing the configuration could work except it
duplicates the already built-in feature of platform configuration, and it would
result in changed files on disk that cannot be committed to git and cannot be
gitignored.
IMHO the platform config is the cleaner approach. If you still don't like that,
then please close this pull request and I'll just keep my vs2013 branch updated
for myself and anyone else who might be interested.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/162#issuecomment-30458287
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
