version control of ISE+EDK projects with CVS and/or SVN

Hello, for the moment, I use SVN to manage different versions of te VHDL code of my projects. I'd like to manage my xilinx projects based on my VHDL code too. Until now, I just put the .ise and .ucf files under version control and it was enough to be rebuild the whole project. Now, I've added an embedded processor to my ISE design and I'm a bit confused because there a huge set of automatically generated files. I'd like to keep under version control just the minimum set of files required to rebuild the whole project. I think there's at least the .xmp, .mhs and .mss files, but is it enough ? Any idea ?

Manu

Reply to
manu
Loading thread data ...

I am afraid, the only way to find out, is to partly delete files and try to reconstruct in order fo find out, what can be thrown away and what should be kept.

Reply to
homoalteraiensis

Theoretically, those should be enough, plus your pcores-directory (in case you have created your own peripherals) and the directory where you store your application code (the C-code for your program).

Putting anything else in the repository will not work smoothly, because EDK deletes whole directory trees when you clean up the project to have it synthesize again.

The implementation directory for example... usually I would like to check in the created netlist files, but once you re-run the EDK flow, EDK deletes the directory including the hidden CVS directories, so your usual CVS client gets really confused...

cu, Sean

Reply to
Sean Durkin

And once again, Xilinx shows their complete antipathy towards any sort of version control ....

-a

Reply to
Andy Peters

Use: ls -uAlF ,ie the last access time of the file(s). Quite hand sometimes to find out which files that are actually used.

might differ for posix systems.

Reply to
pbdelete

.xmp .mhs and .mss is enough to rebuild the edk part. Don't forget any customized linkerscripts/makefiles and, of course, the software source files.

Frank

Reply to
Frank van Eijkelenburg

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.