VisualD can't build x64, Internal error: backend\mscoffobj.c 2016

[Rainer Schuetze via Digitalmars-d-ide]

On 21.03.2017 10:50, ParticlePeter wrote:
 > Single file compilation: (as you suggested) does not compile as a
 > specific module could not be found. Path to that module is NOT in the
 > search paths listed, however, the module IS in the Solution Explorer
 > tree. Shouldn't that be enough for visuald to include it in the
 > compilation process? Moreover shouldn't 'Combined compile and link' have
 > the same issue? Anyway, after adding the path manually the build and
 > link went through and the executable works.

With combined compilation, imports are resolved by modules given on the 
command line first. With single file compilation imports must go through 
the file system and need appropriate import search paths.

>
>> Or try dustmite to reduce the error (see
>> http://rainers.github.io/visuald/visuald/DustMite.html).
>
> Don't get dustmite working, immediately after invoking it complains
> about the first module (first in single file compilation and first
> listed in solution explorer):
> The process cannot access the file because it is being used by another
> process.

It's not clear if it is the problem here, but dustmite integration 
doesn't work with single file compilation (also mentioned in the 
documentation). Maybe there is also a problem if the source files are 
located somewhere completely different (as the issue with single file 
compilation suggests).

>
> I made sure that no other processes are running, in particular ST3 with
> DCD.
>
> Anyway my issue is sufficiently solved, I can work with that. But if you
> still want to look into it I am happy to assist.

If your code is publicly available somewhere, I can have a look. Having 
mscoffobj.c error out depending on -c is pretty strange.