Mirror of forum.nim-lang.org

5442 :: build*.exe with pictures, icons...

• Peter58 (orginal) [2019-11-03T06:53:04+01:00] view original

  Can we compile a script by directly embedding images and / or icons in the the * .exe file... instead of having them separately?

---

• juancarlospaco (orginal) [2019-11-03T08:16:21+01:00] view original

  staticRead

---

• Araq (orginal) [2019-11-03T09:45:07+01:00] view original

  For the exe icon you need to use a resource compiler and code like (taken from koch.nim):

  when defined(gcc) and defined(windows):
    when defined(x86):
      {.link: "icons/koch.res".}
    else:
      {.link: "icons/koch_icon.o".}
  
  when defined(amd64) and defined(windows) and defined(vcc):
    {.link: "icons/koch-amd64-windows-vcc.res".}
  when defined(i386) and defined(windows) and defined(vcc):
    {.link: "icons/koch-i386-windows-vcc.res".}
  Run

---

• akavel (orginal) [2019-11-03T17:45:00+01:00] view original

  IIRC the compiler in GCC is named "windres.exe". Or was it in Visual Studio?

---

• aredirect (orginal) [2019-11-03T17:54:04+01:00] view original

  I encourage you to give nimassets a try https://github.com/xmonader/nimassets

---

• shashlick (orginal) [2019-11-03T18:47:44+01:00] view original

  Alternative is https://github.com/genotrance/nimdeps.

---

• Peter58 (orginal) [2019-11-04T07:31:54+01:00] view original

  Yes, nimassets seems easy and interesting ... But the * .exe is it really standalone? What happens after the build, if I erase all the directory "templatesdir"? The * .exe will still work?

---

• aredirect (orginal) [2019-11-04T18:32:18+01:00] view original

  yeah, the idea of nimassets is compiling all of your assets into a nim file that will be compiled as part of your executable (check its mechanism here https://xmonader.github.io/nimdays/day14_nimassets.html)

---