If I'm not mistaken ( and I hope not, cause it's cost me some time and bugs a few times now ), there's no automatic updating system or versioning system yet. I update using BeyondCompare 2, and it's manageable using that tool. Create a new mod from scratch, and merge that with your source tree. Only the files modified on both ends should require a manual merge.
Expect some work though, since more often than not some core interfaces have changed and you'll also need to change all calls using the new interface in your modified code. There's also a fair chance that after the merge you've introduced some bugs that are, let's say, less fun to track down. These are mostly due to e.g. interfaces that have changed in base classes you've in the meantime derived from (so the derived class's function won't be called anymore), etc. hth, maarten > This is a multi-part message in MIME format. > -- > [ Picked text/plain from multipart/alternative ] > I would assume there updates to the Source SDK, but let's say VALVe > releases an update for the source code, would MY source update aswell? Or > would i have to re-create a mod and apply the updates myself? Then the > second question, on the VALVe dev wiki, under the "SDK Known Issues List". > There's some fixes that look like: > > "--- src/public/studio.cpp 26 Aug 2006 21:24:47 -0000 1.3 > +++ src/public/studio.cpp 27 Aug 2006 19:44:53 -0000 > @@ -783,7 +783,7 @@ > > mstudioseqdesc_t &CStudioHdr::pSeqdesc( int i ) const > " > > Is this for a program to automaticly add/remove code? (Diff and patch?) > -- > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlcoders > > > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
