-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ActiveHDL 10.2 not detected #148
Comments
This worked on windows, allowing me to use
and
|
I think we should listen to a a {SIMULATOR_NAME}_PATH environment variable to let the user explicitly set the executable PATH in any case. |
One thing which you can possibly take advantage of is that there is no Active HDL for Linux: https://www.aldec.com/en/support/resources/documentation/faq/1742 |
@joshrsmith Ok based on this information the rule can be: |
Great! This appears to be working. Versions 9.3, 10.1, 10.2 are being correctly detected, as are Riviera versions. Active HDL versions 9.3, 10.1 and 10.2 are all passing acceptance tests as well. |
Good news. Thank you! |
…able to explicitly set simulator executable prefix. Closes #148
It appears in Active HDL 9.3, there is
vsimsa.bat
andVSimSA.exe
, but in 10.2 it changed tovsimsa.bat
andvsimsa.exe
.When running VUnit against ActiveHDL 10.2 it does not detect the simulator. It looks for VSimSA (case sensitive), which it does not find.
As a possible fix, I changed the search to use
vsimsa
, which allows ActiveHDL to be detected, but this then causes confusion between RivieraPRO and ActiveHDL since they use the same method of detection (e.g. even if VUNIT_SIMULATOR=rivierapro then ActiveHDL will be used if first on the path).One difference between activehdl and riviera is that activehdl bin directory has
avhdl.exe
and riviera hasriviera.exe
(this is on windows -- not sure how it looks on Linux). However, even if the two simulators can be successfully detected and differentiated, then an absolute path will be needed to invokevcom
andvsim
, because otherwise the order in the system path will take precedent.Related questions:
The text was updated successfully, but these errors were encountered: