Noop , I don't think its java
It defines a method of discovering an CM system and allowing the IDE to call generic version control actions such as check in , add, remove ver etc ,
Most of the enterprise version control tool are scc complient and thus can bind to any IDE whish also supports it..
Probably com based, C++
I am sure you can do better .
If you change the compiler then the correct procedure would be to reset the tool varialble CC_HOME in the global.mk file at the top of the tree. Changing the global.mk will cause a full rebuild.
Yes you can change the compiler with an environment variable and overide the global.mk file but this is not good procedure as user environment variable are not under version control unless you have a common environment which is all that is supported.
So keep global.mk secure and change the tools in this file causing the correct rebuild behaviour.
Look , nmake , builder and gmake all have the vpath concept.
I can use nmake in a view/vob and make my binaries available for the rest of the team.
This allows for nightly and incremental building just fine.
Yes all true... and I know cos i was there.
Sablime is great, but a little clunky and limited in branching. It frightens most CC admins away. this tool is also on sale now... Poor LU.
However Rational still struggle to come up with as good Cahnge management system
People make SCM work and they use tools
David , it sounds like you were working in a team full of pretend CCadmins and engineers. Obviously nobody had even read the manual !!
I blame teh management for allowing this to happen . You sem to blame the tool...
MicroSoft also has a bag full of ClearCase licenses aswell 600 . So there U have it . They have all the tools they need and yet....
SourceDepot is apparently a cover for p4. Wouldn't want to take away any VSS sales.
the Rational story is that ClearCase is under all VSS application development.
Noop , I don't think its java It defines a method of discovering an CM system and allowing the IDE to call generic version control actions such as check in , add, remove ver etc , Most of the enterprise version control tool are scc complient and thus can bind to any IDE whish also supports it ..
Probably com based, C++
I am sure you can do better .
If you change the compiler then the correct procedure would be to reset the tool varialble CC_HOME in the global.mk file at the top of the tree. Changing the global.mk will cause a full rebuild. Yes you can change the compiler with an environment variable and overide the global.mk file but this is not good procedure as user environment variable are not under version control unless you have a common environment which is all that is supported. So keep global.mk secure and change the tools in this file causing the correct rebuild behaviour.
check out the MS SCC interface standard
Microsoft use p4 for some things and use clearcase for others . Suspected SCM platform for VSS is clearcase. Any other info ???
Look , nmake , builder and gmake all have the vpath concept. I can use nmake in a view/vob and make my binaries available for the rest of the team. This allows for nightly and incremental building just fine.
Yes all true ... and I know cos i was there.
Sablime is great, but a little clunky and limited in branching. It frightens most CC admins away. this tool is also on sale now ... Poor LU.
However Rational still struggle to come up with as good Cahnge management system
People make SCM work and they use tools
David , it sounds like you were working in a team full of pretend CCadmins and engineers. Obviously nobody had even read the manual !! I blame teh management for allowing this to happen . You sem to blame the tool ...
MicroSoft also has a bag full of ClearCase licenses aswell 600 . So there U have it . They have all the tools they need and yet ....
SourceDepot is apparently a cover for p4. Wouldn't want to take away any VSS sales.
the Rational story is that ClearCase is under all VSS application development.