Mysterious syntax error with "set" command in TCL script

Another Linux vs Windows issue. We have a TCL script that works under Linux when we use "vitis -s <scriptname>", but it gives us problems at the following line under Windows. Any idea what's going wrong here?

Top Replies

Jan Cumps over 1 year ago +1

/temp/workspace is most likely not a windows root directory.
quadzilla over 1 year ago +1

Found the problem. A co-worker let me astray when he said we should use "vitis -s". I had to dig deeper to learn that this is only for Python scripts. In othe words, it was a documentation error on his…

dyessgg over 1 year ago

I'm assuming you're moving the file between the platforms in a way that converts the line endings.

It would be helpful to see a few lines above and below the offending line.

Maybe try turning on your editor's option to visualize "white space" characters. There might be something lurking there Windows doesn't like.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Jan Cumps over 1 year ago

/temp/workspace is most likely not a windows root directory.
Cancel
Vote Up +1 Vote Down

Sign in to reply

Cancel
quadzilla over 1 year ago in reply to Jan Cumps

No, c:/temp/workspace definitely exists.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
quadzilla over 1 year ago in reply to dyessgg

Since you asked, this is what Notepad++ shows me. I don't see anything unusual there.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
shabaz over 1 year ago in reply to quadzilla

Are there any TCL commands above the snippet you supplied? Maybe the TCL interpreter isn't invoked and Windows is executing it as a different script, throwing the error. You could test with other TCL commands. It's been a decade since I last used TCL so I cannot remember a single TCL command any more : (
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
quadzilla over 1 year ago in reply to shabaz

Nope. Those are the very first lines.

Could Vitis not be invoking the TCL interpreter? I suppose so, but I wouldn't know how this could happen or why.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Jan Cumps over 1 year ago in reply to quadzilla

yes but that's not /temp/workspace
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
quadzilla over 1 year ago

Found the problem. A co-worker let me astray when he said we should use "vitis -s". I had to dig deeper to learn that this is only for Python scripts. In othe words, it was a documentation error on his part. Sorry for the confusion, and thanks everyone.
Cancel
Vote Up +1 Vote Down

Sign in to reply

Cancel
padudle over 1 year ago

I think you should make that a relative pathname like ./temp/workspace/system_build.xsa for better portability.

Sometimes putting the path in {} brackets helps. I think it tells Xilinx TCL to convert to the native path format of the local machine.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel