Solved!
In the previous step, I learned that the **cross-compile arguments MUST be on
the command line** , they cannot be in `nim.cfg`. Combine this with the
following.
The next clue in this puzzle was to try the arm_sandbox project on another
Windows10 machine . . . and it worked. I narrowed
I've found a clue to this puzzle, but still can't find a solution. When I
compile with my cross-compile arguments on the command line, I get a different
result than if I compile with the cross-compiler .exe as the only command line
argument and the remaining cross-compile args in the `nim.cfg`.
A solid guess, but that doesn't seem to be it. After copying the toolchain to a
path without spaces and adding that to `PATH`:
D:\code\nim\arm_sandbox> nim c
--arm.standalone.gcc.exe=arm-none-eabi-gcc.exe .\src\before.nim
Hint: used config file 'D:\code\nim-1.6.10\config\nim.cfg
Oh, wait. I only set `PATH` local to that command shell . . . I don't know if
`mingw` will use the shell's `PATH` or the system `PATH`. Let me retry.
I have a [project](https://github.com/dwhall/arm_sandbox) that builds a very
simple program via cross-compiling using the arm-none-eabi-gcc toolchain. Most
cross-compile options given to nim are in the project's `nim.cfg` only the gcc
binary is given on the command line. On a MacOS host, `nim` f
Maybe it's the spaces in your path.
