Can't import compiler/* anymore

2023-05-12 Thread ElegantBeef
> a separate library as before In my experience a separate library never worked. You want to use the compiler API of the compiler you are using. I had many issues with Nimscripter and `requires "compiler"` there's just not a good way of requiring the version of the API your compiler is. This wo

Can't import compiler/* anymore

2023-05-12 Thread dPixie
@Araq what is the correct way to handle a Nim project that needs access to the compiler library files going forward? Since including a Nimscript runner in your binary requires it (unless I'm mistaken) it would make sense that it was part of the distribution of Nim std, or a separate library as b

Can't import compiler/* anymore

2023-05-11 Thread Araq
I frequently build Nimble on a system which lacks Nimble. I use the `koch` tool to do it.

Can't import compiler/* anymore

2023-05-11 Thread sls1005
Another problem is that `nimble` requires `compiler/*`. While `compiler` is not shipped with Nim, but as a Nimble package, it has to be installed via `nimble`. Thus we cannot build `nimble` on a system where `nimble` is not built, because it itself depends on a Nimble package.

Can't import compiler/* anymore

2023-05-11 Thread shirleyquirk
What would the best way forward be, then. > The 'compiler' directory should be placed in /usr/lib/nim ?.

Can't import compiler/* anymore

2023-05-11 Thread federico3
This is related to \- the last line indicates: > The "compiler" directory contains compiler sources and should not be part of > the compiler binary package This is also related to and it impacts

Can't import compiler/* anymore

2023-05-11 Thread dPixie
Thanks @ElegantBeef and @pietroppeter. I did see the path option while researching this, but since they folded the `compiler` package into `nim` I assumed it would be reachable through that package now - guess the cake is a lie yet again :D The `"$nim"/compiler/[ ... ]` works. Thanks for helpin

Can't import compiler/* anymore

2023-05-11 Thread pietroppeter
a similar issue was raised some time ago by a nimib user (nimib uses module `pathutils` which is under compiler's namespace): in that case the problem was that nim was installed on archlinux through distro's package manager related nim's repo i

Can't import compiler/* anymore

2023-05-10 Thread ElegantBeef
Nimscripter uses the compiler API and used to do `--path:"$nim"` which adds the required path(assuming your compiler shipped the source code). Now it just does `"$nim" / compiler /[...]`. Both of those though depend on your Nim distribution. So what OS are you on and how did you install Nim?

Can't import compiler/* anymore

2023-05-10 Thread dPixie
I did a search in the forums, Github issues and Google but I couldn't find any reference to this problem: I have a Nim project that started out in Nim 1.4 or so that I have upgraded over the years to the latest Nim, currently on 1.6.12. The project needs access to som of the compiler internals