> then I guess multilib it's not supported That's bad news!
In theory, on Windows one could avoid adding Nim's `bin` folder to the PATH, and have different batch scripts to add it to the PATH for the current CMD env at usage time, this would allow to chose between Nim 32- and 64-bit. But the problem would remain for the `~\.nimble\` folder though! If there is a way to configure each Nim setup to have Nimble handle packages in custom folders, then maybe dual setup would be possible. I haven't found any references in Nim documentation regarding this; I would though it was a crucial question — If one wishes to publish a DLL for both x86 and x86-64 how is he going to do it? Maybe it's just me that I'm missing out something.
