Open monkey-w1n5t0n opened 3 years ago
@lm-w1n5t0n PR welcome, it shouldn't be too hard:
nim danger
+ a few others)Would love to contribute but I've only just started learning Nim, so it will take a while to build up to that point.
Just to clarify, this is not supposed to work? I thought that the nimscript file could store any of the flags that can be used when calling the compiler directly, and I don't see why specifying the output binary location should be an exception.
I misread, i thought you were calling nim e --out:foo main.nims
which should give a CT error since no binary is produced in this case
indeed this should work:
nim c main
with main.nims containing --out:foo
you can build a debug version of compiler as follows https://nim-lang.github.io/Nim/intern.html#rebuilding-the-compiler and get a stacktrace, as a starting point
Seems that the bug was fixed, I can't reproduce it on 2.0.8.
Compiling with
nim c --out:hello_world main.nim
works fine, but adding the--out:hello_world
flag tomain.nims
crashes compilation.Example
Contents of a
recreate.sh
shell script:Current Output
(comments added for clarity)
Expected Output
## Third
should also produce an executable namedhello_world
and run it to printhello world
.Additional Information
Windows 10 Home (using
git-bash
to run the script)