-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
"compiler" directory is required by some Nimrod tools. #1706
Comments
Personally I think the whole compiler should be refactored out into nimble packages. There's lots of little modules there that would make sense as stand-alone nimble packages. But I also think it would be very nice if the compiler was split into a nim library (which could be used directly from tools, IDE's and script libraries if desired, like you can with LLVM) and a nim compiler tool. Only issue is how you would bootstrap this setup. But I think it could be worth it. |
@skyfex: What's in the compiler that would be beneficial as a general purpose nimble package? I'm not very knowledgeable about what's actually in compiler. @Araq, @dom96: Any word on this? 0.10.2 is out and contains this bug. To me this is High Priority as it breaks c2nim, and I figure lots of people will test out C integration when experimenting with Nim. |
c2nim now finally works via Nimble so I consider this fixed. |
Thanks! Good enough for me as a package maintainer. Eventually I'd like to see @skyfex's suggestion implemented, but that's for another day. |
@philip-wernersbach In progress: #623 |
Some tools like c2nim use files from the "compiler" directory, but the compiler directory isn't installed when issuing a
koch install
. The workaround is to copy the compiler directory to the Nimrod install directory manually, which we have to do for Homebrew/legacy-homebrew#34693.There should be a better system of sharing the files in compiler with the tools that need them. I'm not sure that modifying koch to do a wholesale copy of the compiler directory would be beneficial here, since the amount of tools that rely on these files is small.
The text was updated successfully, but these errors were encountered: