Am I the only one to be shocked to get an SDK updated often ? I mean... The HL1 SDK didn't have so many update.
I'm a little disapointed of this, as I'm having an unfinished product... Will we have a continous updated SDK, forever ? I dislike this method, and prefer to know now, in place to work on this solution. Thanks. -----Message d'origine----- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Mike Dussault Envoy� : vendredi 18 f�vrier 2005 19:00 � : [email protected] Objet : RE: [hlcoders] SDK Code update. It's recommended that you merge the latest code from Valve into your mod, but it's certainly not required. We keep our interfaces backwards compatible. When we release new code, we figure people will merge it at an appropriate time for them. Merging our changes can be made much easier by using a source control system like Perforce or CVS. I'm writing a document on this (should be out next week), but in a nutshell, you do this: 1. Make a branch (branch A) that holds Valve's latest source drop only. 2. Make a branch off branch A that holds your source code (call this branch B). 3. Edit your code in branch B. 4. When a new Valve update comes out, copy all Valve's latest code into branch A and integrate the changes into branch B. If you do it this way, the source control program will handle the lion's share of the merge work for you (depending on how much of Valve's base code you've modified). _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
