Mirror of forum.nim-lang.org

3568 :: Discussion: Nim system integration (linux)

[2018-02-21T17:41:58+01:00]

Demos (orginal) [2018-02-21T17:41:58+01:00] view original

Couldn't render post #22270.

dom96 (orginal) [2018-02-21T17:54:40+01:00] view original

Some relevant things:

Nim already expects global Nimble packages in /opt/nimble/pkgs (https://github.com/nim-lang/Nim/blob/devel/config/nim.cfg#L49)

This issue has a lot of relevant discussion https://github.com/nim-lang/nimble/issues/80

Demos (orginal) [2018-02-21T18:16:30+01:00] view original

Ah didn't know that. Still I propose /usr/include/nim for packages that are handled by your system's package manager and not nimble.

I figure nim doesn't need to look there by default, just encourage packagers to add it to the nim config. My meson work doesn't really use nimble at all, and I indent to disable nim's nimblepath features. (along with {.dynlib.} for import.)

Demos (orginal) [2018-02-24T20:12:49+01:00] view original

OK, I guess I'll make a github repo with some examples and proposals then. I want to make an example meson based project so people can comment on the meson implementaiton (it's nim is unique here since it compiles to C, and I want to have meson deal with that C instead of nim. This way nim can integrate with C/C++ code much more easily.