I want to trace the main script to get more insight how this works, so I wonder if attach a debugger would be a good idea. I can't run tkrev itself form the sourcecode, because differences in initialization, so I'm trying to attach the ActiveState Debugger to it, opening eclipse by one side and debugger in the other, but I can't make them talk. Any suggestion?
So this would neccesarily need some modifications to work... Vivado despite all has its own project structure and commands to get the necessary files to get it working. However If one does source control manually is almost impossible to reuse this directory structure, because command generated files and user files lie in the same folders... and some folders regenerate automatically, so an external tree must be generated, and precisely that is that I want to avoid. It would be feasible to make a fork...
Hi I'm using an EDA program (Xilinx Vivado) that uses Tcl for scripting. This IDE lacks version control systems integration. Can I have some advice trying to integrate tkrev through a tcl console?