search for: public_svn

...but I figure we'll hit it sooner or later on one of the bots as people start > to use 2013 so best to deal with it sooner. Essentially, when building any > configuration through ninja with debug data enabled with anything more than > -j1 we'll hit an error like: > > C:\work\public_svn\llvm\lib\Support\APInt.cpp : fatal error C1041: cannot > open program database > 'c:\work\public_svn\build-vs2013-native-ninja\lib\llvmsupport.pdb'; if > multiple CL.EXE write to the same .PDB file, please use /FS > > Here's the relevant CMake tracker which shows the fix...

...later on one of the bots as people start >>> to use 2013 so best to deal with it sooner. Essentially, when building any >>> configuration through ninja with debug data enabled with anything more than >>> -j1 we'll hit an error like: >>> >>> C:\work\public_svn\llvm\lib\Support\APInt.cpp : fatal error C1041: cannot >>> open program database >>> 'c:\work\public_svn\build-vs2013-native-ninja\lib\llvmsupport.pdb'; if >>> multiple CL.EXE write to the same .PDB file, please use /FS >>> >>> Here's the re...

Yes. I’ll handle the documentation updates too. I’ll base the list of C++11 features on the MSDN documentation. -Chris > On Jan 30, 2015, at 3:57 PM, Aaron Ballman <aaron at aaronballman.com> wrote: > > On Fri, Jan 30, 2015 at 6:51 PM, Chris Bieneman <cbieneman at apple.com> wrote: >> +Alex Bradbury >> >> Sounds to me like we have no known users still on

On Fri, Jan 30, 2015 at 6:51 PM, Chris Bieneman <cbieneman at apple.com> wrote: > +Alex Bradbury > > Sounds to me like we have no known users still on VS 2012. > > So, how about we plan to move forward again with Chandler’s proposal for making this transition. For those who don’t want to dig through to the beginning here’s the basic plan: > > 1) Loop in cfe-dev and

Just started looking at the Story Runner integration, and am converting a few Rails integration tests to get a feel for it. My integration tests relied on fixtures, and since my models have a significant amount of validation (and hence need valid data unless I save without validation), this has made setup easy. With stories however, I''m wondering what the recommended approach is.