Mirror of forum.nim-lang.org

6586 :: Compile w/o using parent directory configs

• GoldtoothFour (orginal) [2020-07-24T00:10:58+02:00] view original

  Beginner here.

  I'm trying to compile a simple binary (nim c binary.nim) without using parent directories' config.nims or nim.cfg but it seems --skipCfg and friends don't do anything. What am I missing?

---

• SolitudeSF (orginal) [2020-07-24T08:21:41+02:00] view original

  --skipParentCfg:on

---

• GoldtoothFour (orginal) [2020-07-24T09:29:04+02:00] view original

  Tried that and skipCfg and skipUserCfg and skipProjCfg.

---

• geotre (orginal) [2020-07-24T17:24:17+02:00] view original

  What is the output when you run the command?

---

• GoldtoothFour (orginal) [2020-07-24T23:16:28+02:00] view original

  It builds using the switch configs in the parent dir's config.nims: if I run nim c -r --app:bin --out:binary --skipParentCfg:on in the util folder, it compiles a library using the parent dir's config.nims and tries to run the resulting *.so. My project structure looks like:

  
  src
  |  pkgname
  |  |  util
  |  |  |  binary.nim
  |  |  config.nims
  |  |  ...
  |  pkgname.nim
  pkgname.nimble
  Run

---

• geotre (orginal) [2020-07-27T18:10:33+02:00] view original

  When using the run flag (-r) the arguments after the module name are passed to the compiled program. You need to put all arguments meant for the compiler before binary.nim.

  Instead of this:

  c -r binary.nim --app:bin --out:binary --skipParentCfg:on
  Run

  Try:

  c -r  --app:bin --out:binary --skipParentCfg:on binary.nim
  Run

---

• jibal (orginal) [2020-07-27T22:41:42+02:00] view original

  Fix your program (binary.nim) to report bad command line arguments and you will avoid spending time scratching your head over this sort of thing.

---