We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

AR# 61037

2014.2 Vivado - Archive project and Copy Runs do not bring in tcl.pre and tcl.post script files


Under Project Settings I can add Tcl script files to be run before (tcl.pre) or after (tcl.post) the following flow processes:

  • Synthesis
  • Opt Design
  • Power Opt Design
  • Place Design
  • Post-Place Power Opt Design
  • Route Design
  • Post-Route Phys Opt Design
  • Write Bitstream

If I add a script, it is run properly as part of the process as expected.

However, I notice that I lose connection with the script file under the following conditions:

  • If I archive my project, the script is not included as part of the archive.
  • If I select Copy Runs, the link to the script is not maintained if I am using a relative path.
  • If the Tcl script is pointed to by a relative path, the tools will not be able to find the script if the project is moved.


In Vivado 2014.2 and earlier, the tcl.pre and tcl.post scripts are specified as a property of a run.  

These files are not actually considered as project files.  

Therefore, they will not be added to an archive as a project source and if the tcl.pre or tcl.post process property is set with a relative path, any time the project location or a run location is changed, the property will need to be updated to match.

To include the Tcl scripts as part of the project, you can import the Tcl script with the import_files command and then use a relative path pointer in the project properties.
AR# 61037
Date 02/25/2015
Status Archive
Type General Article
  • Vivado Design Suite - 2014.1
Page Bookmarked