Mirror of forum.nim-lang.org

619 :: How to add nimble's temporary directory to LIBRARY_PATH

• h3rald (orginal) [2014-11-08T21:08:05+01:00] view original

  In one of my nim(rod) programs (https://github.com/h3rald/hastyscribe) I need to statically link libmarkdown.a when compiling. This works, but unfortunately having dependencies like this is a bit of a pain when it comes to redistributing my program via babel (or better, nimble).

  At present, I am currently distributing precompiled versions of libmarkdown.a for some platforms/architectures, and I added the following to my hastyscribe.nimrod.cfg file (https://github.com/h3rald/hastyscribe/blob/master/hastyscribe.nimrod.cfg):

  @if macosx:

  passL: "-lmarkdown_macosx_x86"

  @end

  @if windows:

  passL: "-lmarkdown_windows_x86"

  @end

  @if linux:

  @if arm:

  passL: "-lmarkdown_linux_arm"

  @else:

  passL: "-lmarkdown_linux_x86"

  @end

  @end

  Of course, for it to work the compiler needs to be able to find the files, so I added the following:

  putenv: "LIBRARY_PATH=/tmp/nimble/hastyscribe/vendor:/tmp/nimble/hastyscribe_head/vendor:/private/tmp/nimble/hastyscribe_head/vendor:/private/tmp/nimble/hastyscribe/vendor"

  ...which worked great (well, ok, it's a bit of a hack) until nimble switched from saving downloaded sources in /tmp or /private/tmp, to a random directory.

  How can I get this to work again with nimble? Is there any better way to do this?

---

• gradha (orginal) [2014-11-08T22:44:27+01:00] view original

  If that libmarkdown.a file comes from C source files you can simply add them to your package and use the compile pragma like I'm doing at the end of hoedown.nim, effectively compiling the library along your nimrod wrapper. Seems to work fine.

---

• h3rald (orginal) [2014-11-09T20:23:23+01:00] view original

  Thanks a lot! I will try it out and see how it goes...

---