UPGRADE YOUR BROWSER

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!

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Visitor simonsabato
Visitor
327 Views
Registered: ‎05-19-2018

Cannot define a value on xvlog command line in Windows command prompt

Jump to solution

I seem to be unable to do something very simple: 

C:\>xvlog test.sv
INFO: [VRFC 10-2263] Analyzing Verilog file "C:/test.sv" into library work
INFO: [VRFC 10-311] analyzing module test

C:\>xvlog --define A=B test.sv
ERROR: [XSIM 43-4316] Can not find file: B

This is on Windows 10, using both "new" and "legacy" consoles (properties->options).  Works just fine in Linux.  I think perhaps the various .bat wrappers that get called are not handling the "=". 

Note that it seems to work if I add quotes: 

xvlog --define "A=B" test.sv
INFO: [VRFC 10-2263] Analyzing Verilog file "C:/test.sv" into library work
INFO: [VRFC 10-311] analyzing module test

Is this expected behavior?  I didn't see this in the docs (UG900 etc).  It's hard/impossible to find any command line example of defining a macro *to a value*  (there's lots of "-d MACRO" examples).  

 

0 Kudos
1 Solution

Accepted Solutions
Xilinx Employee
Xilinx Employee
289 Views
Registered: ‎07-16-2008

回复: Cannot define a value on xvlog command line in Windows command prompt

Jump to solution

Yes, the behavior is specific in Windows.

As you've mentioned, please enclose the macro definition in quotes.

-------------------------------------------------------------------------
Don't forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
1 Reply
Xilinx Employee
Xilinx Employee
290 Views
Registered: ‎07-16-2008

回复: Cannot define a value on xvlog command line in Windows command prompt

Jump to solution

Yes, the behavior is specific in Windows.

As you've mentioned, please enclose the macro definition in quotes.

-------------------------------------------------------------------------
Don't forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------