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!

Page Bookmarked

AR# 52951

2012.4 Vivado - GUI forces an absolute path when adding a Tcl file to tcl.pre and tcl.post settings


When adding a Tcl file to any of the tcl.pre or tcl.post selections in the Project Settings for Synthesis or Implementation steps, an absolute path to the TCL file is forced by the GUI and is not updated if the project is moved to a new location. Also, a relative path cannot be entered. For example, under the TCL Console, you will see the following:

set_property steps.route_design.tcl.post {C:\projects\my_proj\my_proj.srcs\sources_1\test.tcl} [get_runs impl_1]


You can work around this issue by using the following commands in the TCL console of the GUI to make the paths relative:

set_property steps.route_design.tcl.post ..\..\my_proj.srcs\sources_1\test.tcl [get_runs impl_1]

Alternatively, you can script this when moving the location of the project to update the path of the project:

set project_path [get_property directory [current_project]]
set_property steps.route_design.tcl.post $project_path\..\..\my_proj.srcs\sources_1\test.tcl [get_runs impl_1]

This set_property command can be applied to any step that uses tcl.pre or tcl.post (synth_design, opt_design, power_opt_design, place_design, power_opt_design, phys_opt_design, route_design, write_bitstream).

This issue has been fixed in the Vivado integrated design environment (IDE) 2013.1.

AR# 52951
Date 01/22/2014
Status Active
Type Known Issues
  • Vivado Design Suite
  • Vivado Design Suite - 2012.2
  • Vivado Design Suite - 2012.3