Actually I'm migrating some mature projects from Xilinx ISE to Xilinx PlanAhead. I need to take advantage of TCL scripting and partitioning of PlanAhead.
This ISE projects are under version control in a SubVersion repository, so I need to define the files that must be under version control but in PlanAhead projects.
On one hand, this question talks about the files needed to put under version control to exactly re-create the implementation results. Even in PlanAhead 13.2 exist the command "File->Archive Project..." that save the sources and other project and option files in a ZIP archive, allowing us identify the files that must be under version control. This is the first choice.
But on the other hand, it is not clear that use this collection of files is the right way to manage a version control for a PlanAhead project. This xilinx forum conversation talk about using a tcl script to re-create the full project, but this script must be maintained apart when a new change is introduced in the PA project
Vivado (son of PlanAhead) have the XAPP1165 application note that talk about version control and recommend put the re-creation TCL script under version control, but Vivado can generate automatically this TCL script.
I would to know which is the best way to version control PlanAhead projects. Identifying needed files or maintaining a re-creation TCL script?
Thank you very much for your responses. Best regards.