The .vh file type vs Xilinx

D

Daniel O'Connor

Guest
I want to add a "header" file that holds a few common functions between
modules and .vh appeared to be the standard, however the ISE project
navigator pukes on it. It appears to be only interested in Verilog files if
their extension is .v...

Have I missed something?

--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
 
Daniel O'Connor wrote:
I want to add a "header" file that holds a few common functions between
modules and .vh appeared to be the standard, however the ISE project
navigator pukes on it. It appears to be only interested in Verilog files if
their extension is .v...

Have I missed something?
Click to expand...
Header files typically are "include" items rather than files in the
project. Leave them out of the project files list but make sure the
macro search path is set to the header file directory if the tool has
any confusion about where those header files are.
 
John_H wrote:
Have I missed something?

Header files typically are "include" items rather than files in the
project. Leave them out of the project files list but make sure the
macro search path is set to the header file directory if the tool has
any confusion about where those header files are.
Click to expand...
That is how I did it and it does work, although PN doesn't notice if I
modify the .vh file which is a bit of a pain.

Guess I should file a bug report with Xilinx :)

Thanks.

--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
 
Daniel O'Connor wrote:
John_H wrote:
Have I missed something?
Header files typically are "include" items rather than files in the
project. Leave them out of the project files list but make sure the
macro search path is set to the header file directory if the tool has
any confusion about where those header files are.

That is how I did it and it does work, although PN doesn't notice if I
modify the .vh file which is a bit of a pain.

Guess I should file a bug report with Xilinx :)

Thanks.
Click to expand...
So it's a bug, why?
 
You must log in or register to reply here.

Welcome to EDABoard.com

Sponsor

Back
Top