Mirror of forum.nim-lang.org

10323 :: linking

• mantielero (orginal) [2023-07-04T18:47:06+02:00] view original

  LVGL is compiled fully every time I compile an example:

  
  nim c -r ex18_styles_to_parts_states.nim
  Hint: used config file '/home/jose/.choosenim/toolchains/nim-1.6.10/config/nim.cfg' [Conf]
  Hint: used config file '/home/jose/.choosenim/toolchains/nim-1.6.10/config/config.nims' [Conf]
  Hint: used config file '/home/jose/src/nimlang/lvgl.nim/examples/config.nims' [Conf]
  .............................................................................................
  /home/jose/src/nimlang/lvgl.nim/examples/ex18_styles_to_parts_states.nim(3, 11) Warning: imported and not used: 'streams' [UnusedImport]
  CC: lv_font_montserrat_30
  CC: lv_font_montserrat_46
  CC: lv_font_montserrat_28_compressed
  CC: lv_font_montserrat_12_subpx
  CC: lv_font
  ...
  Run

  The reason is that the library is inteded to be embeded in the binary itself (and that is the reason behind compiles.nim).

  One option would be creating a library (dynamic or static).

  But I was wondering if I could compile each file during the library installation; maybe with nimble leaving the .o files within the nimble folder structure.

  But later, how I could link those files to the binary. Any {.passL.} flag? Maybe with gorge ?

---

• SpotlightKid (orginal) [2023-07-04T21:40:06+02:00] view original

  LVGL is compiled fully every time I compile an example:

  Is it?

  https://nim-lang.org/docs/manual.html#implementation-specific-pragmas-compile-pragma

  "Note: Nim computes a SHA1 checksum and only recompiles the file if it has changed."

---

• Yardanico (orginal) [2023-07-04T21:43:36+02:00] view original

  As Spotlight said, Nim shouldn't recompile C libraries on every Nim compile. Are you sure you don't have -f (--forceBuild) in one of your .nim.cfg or .nims files?

---

• mantielero (orginal) [2023-07-04T22:32:06+02:00] view original

  In my case is not behaving in a consistent manner. Sometimes it recompiles just the corresponding modified file, but others it recompiles everything.

  https://pastebin.com/Cjtdc1hg

  I am not sure if the issue has to do with the fact that I am jumping from one example to another.

---

• mantielero (orginal) [2023-07-04T22:48:43+02:00] view original

  From what I see, first the ".o" files are created for each example under ~/.cache/nim. Probably in my case would be better to compile all those into the same folder and then to use {.link: "".} instead of compile.

  Does this makes sense?

---

• griffith1deady (orginal) [2023-07-04T22:49:20+02:00] view original

  you can define --forceBuild:off like this: nim c --forceBuild:off main.nim in my case with nimraylib_now this fixed issue

---

• mantielero (orginal) [2023-07-05T19:51:23+02:00] view original

  I will try to see how it behaves

---

• planetis (orginal) [2023-07-05T20:06:39+02:00] view original

  Yes each example has its own "instance" of the static library in its nimcache dir.

---

• mantielero (orginal) [2023-07-06T19:33:59+02:00] view original

  I have created a lvgl.nimble with a task that stores the nimcache outcomes within the nimble structure.

  Later I include a file with the {.link: "xxx.c.o"}. This way there is no need to compile the whole library for each new example.

  It is a bit crappy, but it seems to work.

---