The OpenSTA CVS Repository
CVS is a source control system very commonly used with open source software, it is free, has quite a few client side implementations (including GUIs) and although not without its problems is known to work well. Much more information can be found at:
The very latest versions of OpenSTA are always available from its CVS source repository hosted by SourceForge. The SourceForge page at the following link provides detailed instructions for accessing OpenSTA SourceForge hosted CVS http://sourceforge.net/cvs/?group_id=10857
You can browse the current source in CVS using your Web browser at http://cvs.sf.net/cgi-bin/viewcvs.cgi/opensta
Most of the regular OpenSTA developers use WinCVS available from http://cvsgui.sf.net/ So if you need any hints setting this up to access the OpenSTA sources then ask on the DeveloperMailingList.
There are 2 main ways of accessing the OpenSTA CVS repository: it is most likely that reading this you will only be able to access the 1st way and that is anonymously with read-only access. Full members of the OpenSTA SF project (the core development team) are the only ones to have write access to the CVS repository and only they need to access it in a authenticated fashion. Don't let this deter you though; if you make changes to the OpenSTA source and wish to contribute them back this can be done easily through the DeveloperMailingList, further instructions on this matter are available on the DevelopmentContributions page.
Here a few hints in making use of CVS in your build environment, they may save you a few headaches:
-
Close down Visual Studio before doing a CVS update
-
If a CVS update brings in any new .dsp's or a new FullBuild.dsw then delete FullBuild.opt and FullBuild.ncb before opening Visual Studio again.
-
SF's CVS servers can sometimes be a little overloaded/moody, if a previously working CVS config stops working simply try again a little later.
-
The CVS sources are not always guaranteed to build or work. Although every attempt is made to only commit changes that have had some degree of testing these are not full releases and so problems may creep in. if you come across any issues simply drop a mail to the DeveloperMailingList as it may be that you have hit a problem that others do not know about yet. Keeping CVS buildable is a priority so a fix should soon be committed back to the repository. If you have already found a fix, then all the better, post it to the DeveloperMailingList.
At various times the CVS sources will be tagged to provide known points in time that can be returned to and to create branches within the source code.
ToDo: describe tagging conventions
Of course if you feel like you don't really need the latest and greatest version of the sources then each release is archived for traditional download. If you feel like contributing back to OpenSTA then getting the sources from CVS and easily and efficiently keeping them up to date is really the only way to go.
Once you have the OpenSTA sources, to build them you next need a working build environment...
FrequentlyAskedQuestions
