I tried reverting to Nim 0.11.0, and the libfib.nim.a file was now produced
when I ran compilation. I guess the documentation might be pretty out of date
in spots. However, I still had the same linker errors.
I am able to compile things just fine by passing in the C files directly and
not
Thanks for your reply! could you explain in a little more detail how that
repository answers the question?
I'm trying to compile Nim code to a static library and import it into C. I'm
not trying to import C code into Nim, which is what all the examples in that
repo seem to do.
[https://github.com/juancarlospaco/nim-presentation-slides/tree/master/ejemplos/basico/c](https://github.com/juancarlospaco/nim-presentation-slides/tree/master/ejemplos/basico/c)
Hi all -- I'm using Nim 0.20.2 on Ubuntu 16.04 and reading this page:
[https://nim-lang.org/docs/backends.html](https://nim-lang.org/docs/backends.html)
I'm looking at the code to statically generate a library.
$ nim c --app:staticLib --noMain --header fib.nim
$ gcc -o m
Easiest is to see it here:
[https://github.com/fxcqz/nim-osprey](https://github.com/fxcqz/nim-osprey)
Sorry it’s out of date so some of the .raises fail now (I just removed the ones
that errored and got this)
> I get the following error when trying to compile my code.
Show us your code.
After doing choosenim update stable, and using nim v0.20 I get the following
error when trying to compile my code.
/Users/travis/build/nim-lang/nightlies/nim/e7471cebae2a404f3e4239f199f5a0c422484aac/lib/system/fatal.nim(48)
sysFatal
Error: unhandled exception: intVal is not
> Well, it seems to be easy guessing the problem: He posted "E:New
> folderbinnim.exe" and ""E:New'. OS er..." so the problem may be the space in
> the path name for the nim.exe
More like a backslash vs slash problem for me. Backslash is often used as
escape character and needs to be written
Well, it seems to be easy guessing the problem: He posted "E:New
folderbinnim.exe" and ""E:New'. OS er..." so the problem may be the space in
the path name for the nim.exe. At least I heard of that type of problems years
ago -- I really wonder if that can be an unknown fact for a serious
I know it does not really help, but I am not an Aporia developer, nor a windows
user. But on Linux it does work, and if something goes wrong it would be much
more likely that I could help.
When I wrote my program in Aporia, I clicked on "Compiler & run current file",
this error occurred:
> "E:New folderbinnim.exe" c --run C:UsersDELLDesktopFirst Error: Problem
> occurred during execution: The system cannot find the file specified.
Additional info: Requested command not found:
woops! sorry, newb mistake.
the problem was that the path of another installation of MingW was higher up in
the tree than the nim one. used Rapid Env editor to restructure it and now it
works fine. thanks.
> but my config file says " #gcc.path = r"$nimdistmingwbin""
The `#` means that this line is commented out. I'm pretty sure that the zips
don't include MinGW, just install a newer one.
but my config file says " #gcc.path = r"$nimdistmingwbin""
> Using the zip gives me error with mingw (incompatible version).
Well that seems to be the problem then? You have some outdated GCC in your PATH.
15 matches
Mail list logo
