I also just noticed that building VC10 Cinder in VC12 (with v100 toolset / not updating project) defines _MSC_VER as 1700, thus turning on lots of C++11 stuff (no fault of Cinder).  I've been doing my VC10 stuff in the VC10 environment, so maybe I just haven't noticed until now.

running the git commands, I get this error:

This usually happens when the repository URL starts with "git:", instead of "https:". The "git:"-variant requires me to setup an SSH-server with PuTTy/Pageant and I never got it working. Plus I rather not run any kind of server or service on my computer just to connect to GitHub. Feels like making me vulnerable to hackers (yeah, I am *that* paranoia).

GitHub mentions that using "https:" is the preferred way of doing things, see: 

Would it be possible to change the submodule URLs? If not, could you explain how to setup Git on Windows so it works with the "git:"-variant?

-Paul

I put my armv7/armv7s binaries here, since I think it'll be a couple days before Andrew can rebuild boost.

If cleaning doesn't help, maybe try making sure all settings related to armv7/armv7s are explicit (green), and do the clean/rebuild dance again..

Thanks!

--8

Analysis: http://post.scriptum.ru
Synthesis: http://onewaytheater.us

I had an compile error in one of my recent projects, but after re-creating the VC11 solution, it worked out

Keep up the good work!

Any ideas on this?

Strange part is that with the AppRewrite version from a couple of weeks ago I have no problems, but with this one I have. I ran them alongside on the same machine and the version form about two weeks ago runs fine and loads images. The latest version doesn't.. Strange..

Note that with either one, you can still build your project with support for XP - you just need to change that one setting in the build configuration, which any apt windows developer should know how to do.

One question that I think remains is what to do with the release binaries... but I guess that bridge will br crossed further down the road.

• I fixed a longstanding issue where our _WIN32_WINNT macro was set incorrectly. It now correctly targets Win XP SP2.

• XAudio2 with VC11 is a bit of a mess, as has been covered elsewhere. My new goal is to have the VC 2012 "unboxing" experience be as headache-free as possible. Without rehashing it all, basically we can't use XAudio2 cleanly if users want to support Win <8, without having to install the DX 2010 SDK (which unfortunately has a bug of its own which can be tricky to navigate). I have some preprocessor checks in there now to disable the audio stuff when building with VC11 v110 and to #error out if you attempt to use it from your app. However you can still use VC10, or you can use v110_xp, or you can set your _WIN32_WINNT to Win 8 if that works for your application.

• I fixed the VC11 resources macros (apparently a leading ./ is necessary now)

• I made the MSW resources have proper file path hints

• I fixed the issue @sy1vain brought up above (naming conflict with WIC2's factory class)

I would like to blow away appRewrite soon but let's see how these changes net out first.

-Andrew