Mirror of forum.nim-lang.org

9157 :: Problem with --threads:on

• morturo (orginal) [2022-05-15T17:38:18+02:00] view original

  Just started a new project to learn about threads with nim.

  when isMainModule:
    echo("Hello, World!")
  Run

  When I compile and run it prints "Hello, World!", but if I compile with --threads:on nothing happens. What am I missing here?

---

• PMunch (orginal) [2022-05-15T18:11:04+02:00] view original

  Did you forget -r after adding threads? Both programs should behave exactly the same when run.

---

• r3c (orginal) [2022-05-15T18:13:45+02:00] view original

  Works fine, what is your build command?

---

• morturo (orginal) [2022-05-15T18:36:33+02:00] view original

  I'm using nimble run and I have a nim.cfg at src folder with --threads:on inside.

---

• Yardanico (orginal) [2022-05-15T18:40:35+02:00] view original

  I've just tried creating a new local Nimble binary package:

  
  .
  ├── src
  │   ├── tot
  │   ├── tot.cfg
  │   └── tot.nim
  ├── tot
  └── tot.nimble
  Run

  tot.cfg just has --threads:on.

  And running nimble run works here, it just outputs "Hello, World!" (same as without tot.cfg).

---

• morturo (orginal) [2022-05-15T18:53:47+02:00] view original

  I create a new project and did all those steps again, the problem seem to be with the nim.cfg, if I'm using package_name.cfg it works properly but if I'm using nim.cfg it doesn't works.

---

• Yardanico (orginal) [2022-05-15T19:06:52+02:00] view original

  nim.cfg will always work if you put it next to your main .nim (not .nimble !) file

---

• morturo (orginal) [2022-05-15T19:23:18+02:00] view original

  nim.cfg package_name.cfg

  Two prints showing the result, as you can see the .cfg file is inside the src folder.

---

• morturo (orginal) [2022-05-16T02:21:30+02:00] view original

  This is really strange and disappointing, with a nim.cfg inside src folder with just --threads:on inside I can, inside my "main" nim file have this line var thread: Thread[int], and it will compile but the "Hello World!" message won't appear. If I rename the nim.cfg to package_name.cfg and remove the var thread: Thread[int] line it will compile and show the hello world message. But if I put that line again (var thread: Thread[int]) it won't compile and it will show an error Error: undeclared identifier: 'Thread'.

---

• Yardanico (orginal) [2022-05-16T02:24:53+02:00] view original

  I think this is a bug in how Nimble handles alternative paths for resulting binary files. As a workaround instead of creating config file in the subfolder you can create a nim.cfg (without anything else in the name) in the root folder of your project.

---

• morturo (orginal) [2022-05-17T02:03:17+02:00] view original

  I tried without nimble, using this line nim c --colors:on --path:C:\Users\psore\.nimble\pkgs\lua-1.0 -o:.\bin\server.exe .\src\main.nim to compile my server, this will compile the binary and I can run int with no problems, but if I include --threads:on and compile it, will run and close immediately.

  I copied this line from nimble with --verbose. I will try this on wsl, maybe it's a problem with the windows version...

---