-
Notifications
You must be signed in to change notification settings - Fork 94
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
allow different module names for verilog export #176
Comments
You're right, "filter" or a user supplied name would be better. Nice that someone is using that feature :-) |
Hi, |
In the master branch, the top level module name now is derived from the Verilog file name (lower cased and sanitized i.e. removing all non-alphanumeric characters. Please check whether this works for you, it will also be part of v0.4.0 that will be released in the next 1 ... 2 weeks. |
nice!
…On Sun, 27 Sep 2020 at 19:42, Christian Münker ***@***.***> wrote:
In the master branch, the top level module name now is derived from the
Verilog file name (lower cased and sanitized i.e. removing all
non-alphanumeric characters. Please check whether this works for you, it
will also be part of v0.4.0 that will be released in the next 1 ... 2 weeks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#176 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE223GFPISQRMR6CWUSRCLSH52QRANCNFSM4N3Q7UIQ>
.
--
Matthew Venn
web mattvenn.net twitter @matthewvenn <https://twitter.com/matthewvenn>
|
currently the module is always exported with name top, which tends to interfere with the traditional name of the top level module in any existing project.
would be good to have a box to type the name of the desired module.
The text was updated successfully, but these errors were encountered: