Timothy Normand Miller wrote: > I wouldn't check in the whole project. Xilinx tools have an "archive" > function that will zip up just the files that are needed, leaving out > anything that can be rebuilt. I don't know if Lattice tools have > anything similar. If not, we just need to understand what each of the > files are and collect them together. Also, we should not host them in > the SVN repo, because the project file would be a non-ascii blob. We > can put them on Traversal's web site or something.
I just tried out the archive function and it's useless to us because it archives a lot of unnecessary stuff. Instead, recent versions of ISE introduced .xise files as top-level project files. These are XML files, and together with the source files, they are all you need to recreate an ISE project. As far as I see, this was done explicitly because of customers' endless whining about source control. Furthermore, there's an option to specify where ISE will dump its binary stuff, so that the project directory can remain clean. Unfortunately, last I checked (ISE 11.1), there were problems with passing this path to the various design tools called by the IDE, so on my last project, I just put all my source files into a separate source subdirectory and told SVN to ignore everything but the .xise file in the main project directory. I haven't looked at the Lattice tools, but even if they don't have this, we could nag Lattice about it and use Xilinx as an example. - Viktor Pracht _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
