Differenze
Queste sono le differenze tra la revisione selezionata e la versione attuale della pagina.
Entrambe le parti precedenti la revisione Revisione precedente Prossima revisione | Revisione precedente | ||
vlsi:personalpages:pacher:tmp [30/11/2013 23:36] pacher |
vlsi:personalpages:pacher:tmp [25/03/2014 21:16] pacher |
||
---|---|---|---|
Linea 5: | Linea 5: | ||
+ | |||
+ | [[http://www.egr.msu.edu/~nrm/papers/mwscas2002.pdf|COMPARISON AND ANALYSIS OF DELAY ELEMENTS]] | ||
+ | |||
+ | ====== SVN and Cadence ======= | ||
+ | |||
+ | [[http://www.cadence.com/Community/forums/p/3215/12959.aspx]] | ||
+ | |||
+ | [[http://www.circuitdesign.info/2008/09/pictorial-introduction-to-using-cadence-subversion/]] | ||
+ | |||
+ | [[http://www.circuitdesign.info/blog/2008/08/getting-subversion-and-cadence-to-play-nice-2/]] | ||
====== CVS stuffs for VLSI dummies ====== | ====== CVS stuffs for VLSI dummies ====== | ||
Linea 31: | Linea 41: | ||
This will create a new directory called ''<module name>'' and populate it with the source files. A ''CVS/'' directory inside the | This will create a new directory called ''<module name>'' and populate it with the source files. A ''CVS/'' directory inside the | ||
''<module name>'' directory is used internally by CVS. Normally, you should not modify or remove any of the files in it. | ''<module name>'' directory is used internally by CVS. Normally, you should not modify or remove any of the files in it. | ||
+ | |||
+ | |||
+ | The ''checkout'' command can either take a module name as argument or a path name relative to ''$CVSROOT'' | ||
+ | |||
+ | <code> | ||
+ | cvs co module/path/to/dir | ||
+ | </code> | ||
+ | |||
Linea 87: | Linea 105: | ||
Once you’ve checked a working copy out from the repository, it will remember where its repository is. | Once you’ve checked a working copy out from the repository, it will remember where its repository is. | ||
(the information is recorded in the ''CVS/Root'' file in the working copy). | (the information is recorded in the ''CVS/Root'' file in the working copy). | ||
+ | |||
+ | |||
+ | |||
+ | Users always access the repository through CVS commands, | ||
+ | |||
+ | <code> | ||
+ | cvs [options] <cvs command> [command options] <target> | ||
+ | </code> | ||
+ | |||
+ | |||
+ | The overall structure of the repository is a directory tree corresponding to the directories in the working directory. | ||
+ | |||
+ | |||
+ | Inside the directories are //history files// for each file under version control. | ||
+ | The name of the history file is the name of the corresponding file with '',v'' appended to the end, | ||
+ | |||
+ | ''filename,v'' | ||
+ | |||
+ | All '',v'' files are created with read-only UNIX permissions and you should NOT change the permission of those files. | ||
+ | The directories inside the repository should be writable by the users that have permission to modify the files in | ||
+ | each directory. This normally means that you must create a UNIX group consisting of the users that are expected to edit | ||
+ | the files in a project, and set up the repository so that it is that group that owns the directory. | ||
+ | |||
+ | |||
+ | ==== Creating the repository ==== | ||
+ | |||
+ | To create a repository, run the ''cvs init'' command. | ||
+ | It will set up an empty repository in the CVS root specified in the usual way | ||
+ | |||
+ | <code> | ||
+ | cvs -d /path/to/repository init | ||
+ | </code> | ||
+ | |||
+ | or | ||
+ | |||
+ | <code> | ||
+ | cvs init | ||
+ | </code> | ||
+ | |||
+ | if the ''CVSROOT'' environment variable has been already set. | ||
+ | |||
+ | The ''cvs init'' command is careful to never overwrite any existing files in the repository, | ||
+ | so no harm is done if you run ''cvs init'' on an already setup repository. | ||
+ | |||
+ | |||
+ | ==== Remote repository ==== | ||
+ | |||
+ | |||
+ | <code> | ||
+ | setenv CVSROOT [:method:]hostname:[port]/path/to/repository | ||
+ | </code> | ||
+ | |||
+ | |||
+ | e.g. | ||
+ | |||
+ | <code> | ||
+ | setenv CVSROOT :gserver:cmssw.cvs.cern.ch:/local/reps/CMSSW | ||
+ | </code> | ||
+ | |||
+ | |||
+ | |||
+ | ==== Starting a project with CVS ==== | ||
+ | |||
+ | When you begin using CVS, you will probably already have several projects that can be put under CVS control. | ||
+ | In these cases the easiest way is to use the ''import'' command over an already existing project directory, | ||
+ | |||
+ | <code> | ||
+ | cd /where/you/have/files/you/want/to/install/in/the/repository | ||
+ | cvs import -m "Log message" /where/you/want/them/to/appear/in/the/repository vendor-tag release-tag | ||
+ | </code> | ||
+ | |||
+ | ''$CVSROOT/where/you/want/them/to/appear/in/the/repository'' | ||
+ | |||
+ | Unless you supply a log message with the ''-m'' flag, CVS starts an editor and prompts for a log message. | ||
+ | CVS requires both a ''vendor-tag'' and a ''release-tag'' string, hence they must be present. | ||
+ | |||
+ | |||
+ | ====== Development area ====== | ||
+ | |||
+ | [[vlsi:personalpages:pacher:didattica:ltspice:install|LTspice installation]] | ||
+ | |||
+ | [[vlsi:personalpages:pacher:didattica:ltspice:basics|LTspice basics]] | ||
+ | |||
+ | [[vlsi:personalpages:pacher:didattica:esperimentazioni2:ex1|Traccia 1]] | ||
+ | |||
+ | [[vlsi:personalpages:pacher:didattica:esperimentazioni2:ex2|Traccia 2]] | ||
+ | |||
+ | [[vlsi:personalpages:pacher:didattica:esperimentazioni2:ex3|Traccia 3 (???)]] |