nake doesn't honor ~/.config/nim.cfg

[bkerin]

I tried putting --listCmd in ~/.config/nim.cfg to get a look at exactly how nake ended up invoking gcc but still didn't see any gcc invocations in the output.

[yglukhov]

Does it work when you invoke nim directly from the shell?

[bkerin]

Yes, for basic test binaries at least:

 $ cat hello_world.nim
 echo("Hello world")
 $ echo $LD_RUN_PATH
 /home/bkerin/local/lib
 $ nim compile --run hello_world.nim
 Hint: used config file '/home/bkerin/opt/nim-0.17.2/config/nim.cfg' [Conf]
 Hint: used config file '/home/bkerin/.config/nim.cfg' [Conf]
 Hint: system [Processing]
 Hint: hello_world [Processing]
 Hint: gcc   -o /home/bkerin/projects/upcb/hello_world  /home/bkerin/projects/upcb/nimcache/hello_world.o /home/bkerin/projects/upcb/nimcache/stdlib_system.o

-ldl [Exec]
Hint: operation successful (10989 lines compiled; 0.115 sec total; 17.938MiB peakmem; Debug Build) [SuccessX]
Hint: /home/bkerin/projects/upcb/hello_world [Exec]
Hello world
$ readelf -d hello_world | grep 'Library rpath'
0x000000000000000f (RPATH) Library rpath: [/home/bkerin/local/lib]
$

Following the direction on the git page, NimxApp ens up with this:

 $ readelf -d NimxApp  | grep 'Library rpath'
  0x000000000000000f (RPATH)              Library rpath: [/usr/local/lib]

[bkerin]

And --listCmd in ~/.config/nim.cfg does cause the gcc invocation to show when plain 'nim compile whatever.nim' is used

[timotheecour]

indeed; my settings (eg coloring etc) aren't honored