gpcosim VPI module and iverilog tests now compile on Windows (MinGW64). #124
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Title is self-explanatory. The changes I had to make consist of:
iverilogthought-owas a file, not a command line parameter, when invoked, so all tests usingiverilogwould fail. This seems to be a (currently unfixed as of June 28, 2018) bug. So I swapped command line argument order soiverilogis happy with the command line.VPI_ROOTCMake variable that I expect Windows users to set (the defaults do not make sense on Windows). Even though there are no VPI tests at present, a successful run ofgpcosimcan be seen in the below image.