Mirror of forum.nim-lang.org

4375 :: Application-specific library?

• donallen (orginal) [2018-11-11T19:51:52+01:00] view original

  I would like to create a library specific to a set of applications I have written and am considering porting some of it to Nim.

  I have a small collection of source files in a separate directory that I would like to compile either to object files or go one step further an turn the object files into a library, shared or static. I'm describing something very standard in the C world. I'll ask the simple question first -- how do I compile a nim source file into an object file? I've tried --noMain and --noLinking, to --noAvail :-)

  Once I have the .o files, how do I make them available for importing by source that will be compiled into an executable?

  I know about Nimble packages, but that seems like over-kill for what I want to do here, since the shared code is specific to this suite of applications and not generally useful.

---

• Araq (orginal) [2018-11-12T08:39:26+01:00] view original

  People reported some success via nim cpp --cppCompileToNamespace:myLib but it's generally a bad idea, it's far easier to import your dependencies.

---

• donallen (orginal) [2018-11-12T15:43:22+01:00] view original

  I am already doing what you suggest -- importing dependencies -- but the imported code is in source form. So if I have a utilities.nim file and three of my applications need to use it, I am compiling utilities.nim three times. The real point of my original message was that I'd like to avoid the redundant compilations. Is there a way to do this?

---

• Araq (orginal) [2018-11-13T18:50:33+01:00] view original

  Well as you said, you can try to use static libs for that, but I'd just wait until incremental compilation works.

---