Mirror of forum.nim-lang.org

3354 :: Cannot get glfw-nim to work

• drsneed (orginal) [2017-11-22T00:22:01+01:00] view original

  Hello,

  I'm trying to use this glfw wrapper: https://github.com/ephja/nim-glfw. I clone the repo, enter the examples directory, and execute nim c -r minimal.nim, just as the documentation provides. Compilation succeeds, great! Now I attempt to run minimal.exe but I get a runtime error: could not import: glfwSetWindowUserPointer*

  What I've tried so far:

  1. Ensure glfw3.dll is in the same directory (It is).
  2. Ensure glfw3.dll is 64-bit dll (It is).
  3. Ensure glfw3.dll contains the symbol glfwSetWindowUserPointer (using dependency walker I confirmed this)
  4. Commenting out the wrapper definition of glfwSetWindowUserPointer (I get the same error for other symbols now)

  At this point I don't know what else to try. I'm on Windows 8.1 64 bit running Nim 0.17.2. Any tips would be appreciated. Thank you.

---

• Araq (orginal) [2017-11-22T01:26:51+01:00] view original

  Maybe the calling conventions differ. This usually results in different name mangling rules and so could cause an error like yours.

---

• cheatfate (orginal) [2017-11-22T10:39:44+01:00] view original

  Please, ensure that your executable is also 64-bit.

---

• drsneed (orginal) [2017-11-22T16:08:43+01:00] view original

  The executable is 64-bit. Araq, that would be a logical explanation. Any tips on how I can confirm this? nim-glfw appears to me to use cdecl calling convention, as hinted by this code snippet in glfw.nim:

  proc renameProcs(n: NimNode) {.compileTime.} =
    template pragmas(n: string) = {.glfwImport, cdecl, importc: n.}
    for s in n:
      case s.kind
      of nnkProcDef:
        let oldName = $s.name
        let newName = "glfw" & (oldName[0]).toUpperAscii & oldName[1..^1]
        s.pragma = getAst(pragmas(newName))[0]
      else:
        renameProcs(s)
  Run

  The glfw library also appears to use cdecl calling convention.

---

• drsneed (orginal) [2017-11-22T17:22:07+01:00] view original

  It turns out I had an old nim compiler in my path that was getting used instead of 0.17.2. Once I removed the old compiler, everything works as expected. Case closed.

---