source control and Xilinx ISE 6 and 7

Andy Peters · 2005-04-18T21:50:22+00:00

My quick seach shows that this question comes up occasionally but neverseems to get a decent answer.First, though, an observation: revision/source control systems are anabsolute necessity for any FPGA design of reasonable (andunreasonable!) size. So, why do all of the FPGA vendors GUI toolsetshave rigid but stupid directory structures? I mean, why do the toolsdump compile results, report files, constraint files and the "projectfile" all into the same directory? Why aren't we able to set upreasonable directory structures? For instance, I want my HDL sourcesin one directory, separate from the fitter tool's project directory.(Maybe I want to try the same source with different vendor parts?)Fitter reports should go into a directory of their own. Build results-- the .jed or .pof or whatever results from the fitting -- should goin their own directory. For that matter, what's with hard-coded paths?Complain complain complain. A directory structure like the followingwould be nice:projrootsrc

Apr 18, 2005 20 Replies

Rate this thread:

Ray Andraka 21 years ago

I put the NCD and the generated bitstream in the repository. The ncd because it makes guided revisions possible, as well as getting into the editors, and the bitstream because it is a deliverable with a date on it.

--Ray Andraka, P.E. President, the Andraka Consulting Group, Inc. 401/884-7930 Fax 401/884-7950 email ray@andraka.com http://www.andraka.com "They that give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, 1759

Vote

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required

source control and Xilinx ISE 6 and 7

Related discussions

Why does Xilinx hate version control?

Quartus and source control

creating library in ISE 9

Join the Discussion

Didn't find your answer?