Mirror of forum.nim-lang.org

2981 :: [SOLVED] Specify directory for binary

• void_sleepy_bear (orginal) [2017-06-01T17:55:23+02:00] view original

  When compiling is there a way to specify an output directory for the binary that is produced? for example I am trying to do something like this:

  
  nim c -d:release source.nim some_directory_here
  Run

  I bet there is a way I just can't find the command/options in the manual: https://nim-lang.org/docs/nimc.html

  thanks!

---

• yglukhov (orginal) [2017-06-02T15:54:41+02:00] view original

  Advanced options:

  -o, --out:FILE set the output filename

  This option?

---

• zolern (orginal) [2017-06-02T16:54:58+02:00] view original

  I am afraid -o option doesn't set directory for binary. I tried it when I set my VisualStudioCode to save compiled binaries from all my projects in one folder, but -o expects also filename.

---

• void_sleepy_bear (orginal) [2017-06-03T01:13:07+02:00] view original

  Yeah I did try the '-o' option, and zolern is right it does just expect a file name. The -o option is just to change the name of binary. when I specify a path to -o it just ignores the path given to it and names the binary whatever the source file is named. I tried running the -o option like this:

  
  nim --run c main.nim -o ../bin/program
  Run

  and it returns a binary named main.

---

• jcosborn (orginal) [2017-06-03T04:16:54+02:00] view original

  You need to put the compiler arguments before the source file otherwise it takes them to be arguments to the binary for the run command. This should work

  
  nim --run c -o:../bin/program main.nim
  Run

---

• void_sleepy_bear (orginal) [2017-06-03T07:16:09+02:00] view original

  Thanks jcosborn! that worked for me. it makes sense now.

---

• Libman (orginal) [2017-06-12T03:28:11+02:00] view original

  I like having a little compiler wrapper to execute nim just the way I like it. I wrote one for my needs called nimr [pb], but I think most programmers will want to write their own rather than deal with my fugly old code.

  Some features include:

  • Saves binaries in $NIMR_BIN directory (global env var defined in my ~/.profile, like GOPATH) - which addresses the "-o option doesn't set directory for binary" issue above.
  • Finds the specified program under $NIMR_SRC path, so I can recompile and run any program from anywhere.
  • Usable as a shebanger (#!/usr/bin/env nimr), with ##: compiler option passing (idea taken from someone else's Nim shebanger that I can no longer find).
  • Command variants: when nimr is installed [pb] as nimf (for fast) or as nims (for small) it creates optimized binaries installed.
  • Displays binary size, execution time, and/or errlev info.

---