Mirror of forum.nim-lang.org

4019 :: how to use nimscript for nim.cfg?

• timothee (orginal) [2018-07-06T02:26:09+02:00] view original

  I'd like to use nimscript to replace some of my nim.cfg, to benefit from additional power of nimscript over cfg files (eg defining variables, etc)

  However, my understanding is I can only have a proj_name.nims, not a nim.nims, and therefore the proj_name.nims would only be applied if I compile proj_name.nim, not any other file.

  Could we lift this restriction?

---

• jyapayne (orginal) [2018-07-06T02:42:21+02:00] view original

  @timothee, simply use the name config.nims as recommended here. According to the docs, that should be the equivalent name!

---

• timothee (orginal) [2018-07-06T05:35:52+02:00] view original

  from the docs https://nim-lang.org/docs/nims.html: > For a directory wide configuration, use config.nims instead of nim.cfg.

  this doesn't work recursively:

  
    subdir/
      test.nim
    toplevel.nim
    config.nims
  Run

  
  nim c toplevel.nim # will use config.nims
  nim c subdir/test.nim # will NOT use config.nims
  Run

  This seems like an arbitrary restriction, since nim.cfg itself is recursive, but not config.nims Could we extend it? if there's a use case to make it non-recursive, can we at least have an option to make it recursive? (maybe via some special command at the beginning of config.nims)

---