In Xilinx’ ISE suite, it is possible to delete all files except for a small subset, and the tool gracefully fills the gaps on its next run. This tool is still evolving, so there are significant differences even with respect to 2013.4, and probably related to later version (to be released). Vivado’s revision is assumed to be 2014.1 here. Unfortunately, Vivado’s Tcl script still needs some modifications to function properly in a standalone package. It’s not as difficult as it may appear, since Vivado can output Tcl scripts that regenerate the project’s current state. This page suggest an alternative, which is based upon Tcl scripting. Merging two sets of the project by virtue of manipulating text files is probably impossible with this format, so it’s not very suitable for version control either. ![]() #Add existing vivado project to synplify pro archive#However this file can also reach 20-70 MB, and is hardly suitable for distribution nor version control, even if the ZIP archive is opened into its files: There’s just too much redundancy in the bundle. Vivado has an option to archive an entire project, along with its dependencies into a single ZIP file, which is relocatable, and apparently intended for storing snapshots. Its rather complex behavior as a tool, and the absence of a true file cleanup option require a method to create a compact set of files. Xilinx’ Vivado development system maintains a rather opaque set of files, reaching ~150 MB quite easily for a simple project. with minimal redundancy (so a change in the project is observed in a single file).self-contained (can be used on a fresh computer).Building the project on a remote computer.Distribution of the package to peers and customers.Storing this set in a version control repository (possibly diff-comparing with previous versions).It’s often desired to select a minimal kit of files from an FPGA project under development, which are just enough to build the programming file binary from.
0 Comments
Leave a Reply. |
AuthorBeth ArchivesCategories |