Closed Psirus closed 3 years ago
Did you resolve this? It seems like a configuration issue.
What version of Nim are you using and are you using the nimble esp_build
commands? I've been using Nim version 1.4.4.
No, unfortunately I was not able to resolve this. I am using 1.4.4, but also tried 1.4.0. Didn't try an earlier version since it said 1.4+ in the README. I am using nimble esp_build
. The only thing I forgot to mention was is that I had to change the line
bin = @["esp32_nim_test"]
to
bin = @["src/esp32_nim_test"]
in the nimble file, because otherwise it would error with Error: cannot open 'esp32_nim_test.nim'
. The complete nimble file:
# Package
version = "0.1.0"
author = "Psirus"
description = "A new awesome nimble package"
license = "MIT"
srcDir = "src"
bin = @["src/esp32_nim_test"]
# Dependencies
requires "nim >= 1.4.0"
requires "nesper >= 0.6.0"
include nesper/build_utils/tasks
I was able to replicate the error. I think the master branch generated a nimble file with a bin = @["esp32_nim_test"]
which was a setup I tried earlier but it messes up the build process.
Either way, try updating your Nesper library (v0.6.1 is the new latest on master and devel).
Then remove the bin
line in your nimble file, like:
# Package
version = "0.1.0"
author = "Psirus"
description = "A new awesome nimble package"
license = "MIT"
srcDir = "src"
# Dependencies
requires "nim >= 1.4.0"
requires "nesper >= 0.6.1"
include nesper/build_utils/tasks
Hopefully that should resolve the build issue!
That did the trick! Thank you so much.
Hi, I'm trying to build the example, and I've actually gotten quite far, 807 out of 812 steps in ninja :). However, there is an error now:
The same error appears for "stdlib_io.nim.c.obj" and "stdlib_system.nim.c.obj". For the latter, it also says
Any help would be appreciated. Thanks for this project BTW!
Edit: So it seems nim writes
#define NIM_INTBITS 64
into the start of the generated C code. And as far as I understand it, there should be a 32 there. Maybe it doesn't pick up the--cpu:esp
option for some reason? It is inmain/nim.cfg
.