Indeed, the upgrade from VS2012 is simple, and in fact the VS2013 files can be
loaded in VS2012 as they are backwards compatible. The main difference is which
runtime each one targets, which is a simple change.
My motivation for creating the separate files was so that I could compile for
the VS2013 runtime, which is what my application was using. I imagined that if
anyone else wanted to use libusbx with the VS2013 runtime, they'd be interested
in the same since you are not supposed to mix-and-match C-runtimes.
What would you say about this alternative approach:
Since the VS2013 sln/vcxproj files can still be opened in VS2012 (and maybe
2010?), what if we managed the runtimes through the Solution Configuration
profile? That is what normally says Debug and Release, but you can create other
profiles as well and have project settings specific to each one.
I'm suggesting creating Debug-2012, Debug-2013, Release-2012, Release-2013, and
setting the runtime appropriate for each one. Then there are still only one set
of sln/project files to maintain, but developers can easily target their
desired runtime.
Thoughts?
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/162#issuecomment-30196244
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
