View Single Post
  #15 (permalink)  
Old 05-04-2006, 12:39 PM
avishay
Guest
 
Posts: n/a
Default Re: Quartus and source control

I see that this thread creates lots of interest, but it has gone a
little off topic.

I will try to describe the problem I face in more details. The grup I
work in is composed of several hardware (FPGA) engineers. Some of them
use VHDL, and some use graphic methods. Currently, no source control of
any kind is used, making tracking design sources and sharing them among
the group very difficult. In order to solve some of these problems, I
want to install and start use Subversion as a source control system.
What I look for is a way to automatically include in the source control
components that are normally added in the graphic editor or using the
MegaWizard interface. Another, related problem is taking an existing
Quartus project, and putting it under source control without losing
files and without including files that are not necessary. The best way
to accomplish both tasks, in my opinion, is writing a script that wolud
go through the project hierarchy (after synthesis), pick up all the
source files used and add them to the source control system (if theyr'e
not already there).
Subroto Datta suggested to use the "Source Files Read" section of the
analysis report, which seem to be a good direction, but I need to know
if there is a way to get this information*programatically*, rather than
text processing the report. This report also seem to lack memory
initialization files (maybe more kind of files I don't know of?).

Another type of problem is the SOPC builder. The SOPC builder takes the
system specification from PTF files (as KJ mentioned) and copies HDL
files from the relevant library into the project directory. These
copied files are not strictly sources, but rather intermediate
products, and as such they should not be under the soruce control (they
should, in fact, but they should be controlled by the one that wrote
the component, not the one using them). After SOPC builder has finished
its run, there is no way (to my understanding) to distinguish between
true source files and those who were copied. They will both show up the
same in the said report. A possible solution might be to instruct SOPC
builder to copy its files to a directory other than the project root (I
think it would be much easier to manage also), but I don't know how to
do that.

Thanks for everyone who has replied (and will)
Avishay

Reply With Quote