Mirror of forum.nim-lang.org

7078 :: Best practices for packages that bind to C libraries?

• snej (orginal) [2020-11-12T00:22:13+01:00] view original

  I'm looking for advice on making a Nimble package that wraps a C-based library, where the library will reside in a Git submodule and be contained in the package.

  In other words, I'm not interested in just saying "You have to install libFoobar through homebrew/apt-get/yum/whatever ¯\_(ツ)_/¯" I want my package to build libFoobar and link it into the binary (ideally as a static lib, but a DLL works too.)

  My questions are:

  1. How can I get Nim to build the C library? (I know about the compilec pragma, but what if I need to invoke CMake?)
  2. How do I get the dynlib pragma to find the DLL, when it's neither in the system nor in the current directory?
  3. If I use a static library, how do I tell the linker to add it to the binary?

---

• Clonk (orginal) [2020-11-12T00:33:27+01:00] view original

  Check out nimterop . I think it has been made exactly for that.

---