Mirror of forum.nim-lang.org

10215 :: NIM code compile to executable does not run on other systems.

• nimusertest (orginal) [2023-05-21T20:07:57+02:00] view original

  Hi guys,

  Im trying to compile my nim code to a stand-alone executable. However, the executable I get run perfectly on the machine I just to compile the code, but doesn't run on any other computer. I'm also not getting any errors while running the executable. Its just shutting down within an instant. I'm using the following libaries:

  import dimscord - import asyncdispatch - import options - import os - import strutils - import winim/lean - import winim/inc/lm - import httpclient - import system - import streams - import osproc

  I have already tried many different flags while compiling but nothing seems to work. Could anyone help me? Thanks alot!

---

• matkuki (orginal) [2023-05-22T01:00:02+02:00] view original

  check that all assets your app uses are also on the other machine

  check executable dependencies with dumpbin /dependents <app.exe> in a Visual Studio Command Prompt, and make sure they all are on the other machine

---

• sls1005 (orginal) [2023-05-22T03:50:40+02:00] view original

  Every OS has an executable file format of its own. An executable compiled for Windows cannot be used on macOS. Similarly, an executable compiled for macOS cannot be used on Linux. In addition, every executable is compiled for a specific CPU architecture. One cannot run a x86 executable on a machine with a CPU of ARM architecture. It's possible to run a 32-bit executable on 64-bit system (i.e. a x86 executable on an x86-64 system, or a ARM 32-bit executable on an ARM64 system) but not vice versa. Compiling for a different OS/architecture is called cross-compilation.

---

• Yardanico (orginal) [2023-05-22T05:33:13+02:00] view original

  The first things that come to mind are OpenSSL (because Discord APIs use SSL), and PCRE (I'm not 100% sure, but I think dimscord uses re).

  Try for example starting your app from the windows cmd, you might actually see the problem then. You can find those DLLs in the same folder with the Nim installation on Windows, or get them from nim-lang.org/download/dlls.zip - you need at least cacert, libcrypto, libssl, PCRE, depending on if you're compiling for 64-bit you need to choose the relevant versions.

---

• awr1 (orginal) [2023-05-26T02:24:22+02:00] view original

  Try compiling with --app:gui. If you have DLL errors it will show up as a dialog box instead of popping in an command line which might vanish very fast if you launch from explorer.

  I took a look at your deps and I would concur with @Yardanico, however, looking at the deps for dimscord, I would say the dependency on libsodium is another likely suspect.

---