Comments on: On Build Integrity http://scottbilas.com/blog/on-build-integrity/ Take what you want, and leave the rest (just like your salad bar). Mon, 06 Feb 2012 03:15:56 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Lucas Meijer http://scottbilas.com/blog/on-build-integrity/#comment-292 Lucas Meijer Fri, 02 Oct 2009 20:02:16 +0000 http://scottbilas.com/2009/09/22/on-build-integrity/#comment-292 That's great news. I've always hit some problem when trying to version the compiler. I tried it again today, and am not having much luck. If you could elaborate on how you do this in the follow article, that would be totally great. Bye, Lucas That’s great news. I’ve always hit some problem when trying to version the compiler. I tried it again today, and am not having much luck. If you could elaborate on how you do this in the follow article, that would be totally great.

Bye, Lucas

]]> By: Scott http://scottbilas.com/blog/on-build-integrity/#comment-279 Scott Tue, 22 Sep 2009 21:17:57 +0000 http://scottbilas.com/2009/09/22/on-build-integrity/#comment-279 Yes, this is something I'll be covering in the next post: that every single tool involved in the build must be checked in. No installation required. What do you mean by VS doesn't like to be versioned? This is the third studio I've worked at where we've checked in VC++, and sometimes we've had two or three versions sitting side-by-side in the depot. All you have to do is check in vc/bin, vc/include, and vc/lib. I haven't seen the problem you describe. We don't check in the IDE, though I've done it in the past. The IDE is a source tool, and not involved in builds at all. So while it could go into the depot for convenience, it's not necessary so we don't bother here. Same deal with Maya, Wwise, Photoshop... Yes, this is something I’ll be covering in the next post: that every single tool involved in the build must be checked in. No installation required.

What do you mean by VS doesn’t like to be versioned? This is the third studio I’ve worked at where we’ve checked in VC++, and sometimes we’ve had two or three versions sitting side-by-side in the depot. All you have to do is check in vc/bin, vc/include, and vc/lib. I haven’t seen the problem you describe.

We don’t check in the IDE, though I’ve done it in the past. The IDE is a source tool, and not involved in builds at all. So while it could go into the depot for convenience, it’s not necessary so we don’t bother here. Same deal with Maya, Wwise, Photoshop…

]]> By: Lucas Meijer http://scottbilas.com/blog/on-build-integrity/#comment-278 Lucas Meijer Tue, 22 Sep 2009 18:05:45 +0000 http://scottbilas.com/2009/09/22/on-build-integrity/#comment-278 One of the things that annoys me endlessly about most of the projects I work on, is that Visual Studio doesn't really like to be versioned. Imho, the compiler which compiles a game belongs as much in version control as the sourcecode that is being compiled. Has anybody succesfully versioned visualstudio? (or at least the compiler, I don't really carea ll that much about the IDE) One of the things that annoys me endlessly about most of the projects I work on, is that Visual Studio doesn’t really like to be versioned. Imho, the compiler which compiles a game belongs as much in version control as the sourcecode that is being compiled.

Has anybody succesfully versioned visualstudio? (or at least the compiler, I don’t really carea ll that much about the IDE)

]]>