> The main difference is which runtime each one targets, which is a simple
> change.
Can't you just use a simple search/replace script to update the
`<PlatformToolset>`? I __really__ would prefer avoid adding solution files that
are not going to be used by any of our maintainers for the foreseeable future,
as it's a recipe for sync issues. 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).
On the other hand, I wouldn't have much of an objection adding a script in our
project that replaces all our `<PlatformToolset>v110</PlatformToolset>`
instances with `<PlatformToolset>v120</PlatformToolset>`, to turn the 2012
files into 2013 compatible ones. This might even be possible [in pure
batch](http://www.dostips.com/DtCodeBatchFiles.php#Batch.FindAndReplace). I
also have no objection pushing the .gitignore changes if you need them (though
I'll probably wait until we have another commit to piggyback on that)
NB: I tried removing `<PlatformToolset>` from our existing 2012 files, in the
hope that VS would simply fill the missing part with the latest, but it
complains on open. I also tried setting it to `v120`, in case Microsoft
actually tried not to screw their VS users and planned ahead for a change, but
while it opened just fine in 2012, it produced errors during compilation.
/Pete
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/162#issuecomment-30279160
------------------------------------------------------------------------------
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
