[p4] question regarding SCM procedures

Chuck Emary chuck.emary at Configuresoft.com
Tue Aug 21 08:43:45 PDT 2007


Hello,
We do not store user specific dev environment files, for example, *.suo files, other than that we keep *.dsw, *.dsp, and *.sln files.  This way we can recreate the build artifacts at any point in time.  Hope that helps.

Cheers,
Chuck Emary

-----Original Message-----
From: perforce-user-bounces at perforce.com [mailto:perforce-user-bounces at perforce.com] On Behalf Of Oren Shemesh (oshemesh)
Sent: Monday, August 20, 2007 10:14 PM
To: Kilaru Sambaiah; perforce-user at perforce.com
Subject: Re: [p4] question regarding SCM procedures

Store them the same way as the source code.
If you ever need to rebuild your product from source control, you will
need them, right ?

Oren.

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Kilaru Sambaiah
Sent: Monday, August 20, 2007 3:38 PM
To: perforce-user at perforce.com
Subject: [p4] question regarding SCM procedures

Hi All,
  I have one general question on SCM ( not particular to Perforce ).  I
came
from plain old
  setup of storing .c and .h files, makefiles and generating .exe or .so
files from makefiles.
  We don't need to store .exe or .so files.

 We are planning to use eclipse CDT and thinking how to store project
related files.
  Eclipse or any other IDE will contain .eclipse or .dsw ( in Microsoft
case
).
  My question is
  i) What is your strategy to store IDE related data?

thanks and regards,
Sam
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user




More information about the perforce-user mailing list