search

beef331 / nimscripter

Quick and easy Nim <-> Nimscript interop
MIT License
149 stars 8 forks source link

Add compiler deps #23

Closed elcritch closed 1 year ago

elcritch commented 1 year ago

This unfortunately doesn't appear to resolve the issue. :/

It seems that with Nimble v0.14.2+ that the compiler package has been renamed. Cool except it also doesn't appear to find the compiler package and pass it properly anymore. There's no way to specify the compiler with the new package name. 🤷 😮‍💨

See https://github.com/nim-lang/Nim/issues/21546 and https://github.com/nim-lang/Nim/issues/21545 .

Alas, gonna have to stick to 1.6.10 for a while.

beef331 commented 1 year ago

Yep, regardless I'm never going to accept requires "compiler ..." as it does not use the compiler api of the version you use. Passing --path:"$nim" still is the only good way to use the compiler api.

elcritch commented 1 year ago

Yep, regardless I'm never going to accept requires "compiler ..." as it does not use the compiler api of the version you use. Passing --path:"$nim" still is the only good way to use the compiler api.

That make sense, though it does sorta break using it with Nimble. I'd completely missed the --path:"$nim" piece as well.

beef331 commented 1 year ago

It sucks, but there is no way for Nimble/Nim to load the config from a dependency(for good reason), so it is what it is sadly.

elcritch commented 1 year ago

Yah that makes sense, if a bit annoying. The compiler package worked with the older Nimble too, so I'd completely missed the bit about the path configs the first time.

But thanks, the path option will let me move to the 2.0-rc! Well once I update ants with a proper config.nims.