You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both @c-blake and I tried to find a way to convince Nimble to install a package that has two .nim files where both files are supposed to be both Nim modules and binaries. In other words, both modules contain a when isMainModule statement.
On the Nimble side, I don't know if #747 is somehow related. That ticket describes a different problem though.
What I'd like is a suggestion for a working package setup for hldiff and if possible an explanation for this setup, so we can transfer this knowledge to future packages. Once we have found a suitable setup, it'll probably make sense to update the Nimble readme to contain the necessary background information to arrive at this setup.
The text was updated successfully, but these errors were encountered:
To add to that, there are efforts being planned to change how Nimble installs packages which will hopefully avoid these kinds of problems. CC @genotrance
So I just tried hldiff and it works fine with no errors, I presume this specific issue can be closed. The pkg suffix issue is already being tracked in #308.
Both @c-blake and I tried to find a way to convince Nimble to install a package that has two
.nim
files where both files are supposed to be both Nim modules and binaries. In other words, both modules contain awhen isMainModule
statement.The package in question is https://github.com/c-blake/hldiff . I had opened a ticket there which contains a discussion of our so far unsuccessful attempts.
On the Nimble side, I don't know if #747 is somehow related. That ticket describes a different problem though.
What I'd like is a suggestion for a working package setup for
hldiff
and if possible an explanation for this setup, so we can transfer this knowledge to future packages. Once we have found a suitable setup, it'll probably make sense to update the Nimble readme to contain the necessary background information to arrive at this setup.The text was updated successfully, but these errors were encountered: