www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - VisualD / fatal error C1905: Front-End and Back-End are not compatible (have to use the same processor)

reply =?iso-8859-1?Q?Robert_M._M=FCnch?= <robert.muench saphirion.com> writes:
I try a cross-post from an older post here as I didn't recveive any 
answer in D.learn and I don't have any clue how to solve this:

==> START

A project I can compile via the command line and dub, gives an error in 
VisualD. I created the VisualD configuration through dub:

fatal error C1905: Front-End und Back-End sind nicht kompatibel 
(müssen den gleichenProzessor verwenden).

This translates to: "Front-End and Back-End are not compatible (have to 
use the same processor)"

Well, I don't have a clue what this should mena, nor how this could 
happen. It sounds a bit like if the compiler & linker are not useing 
the same architecture (I want to use x64) but I didn't find any options 
to check/change this.

Any ideas?

-- 
Robert M. Münch
http://www.saphirion.com
smarter | better | faster
Jul 01 2018
parent =?iso-8859-1?Q?Robert_M._M=FCnch?= <robert.muench saphirion.com> writes:
On 2018-07-01 07:10:07 +0000, Robert M. Münch said:


 I try a cross-post from an older post here as I didn't recveive any 
 answer in D.learn and I don't have any clue how to solve this:
 
 ==> START
 
 A project I can compile via the command line and dub, gives an error in 
 VisualD. I created the VisualD configuration through dub:
 
 fatal error C1905: Front-End und Back-End sind nicht kompatibel 
 (müssen den gleichenProzessor verwenden).
 
 This translates to: "Front-End and Back-End are not compatible (have to 
 use the same processor)"
 
 Well, I don't have a clue what this should mena, nor how this could 
 happen. It sounds a bit like if the compiler & linker are not useing 
 the same architecture (I want to use x64) but I didn't find any options 
 to check/change this.
 
 Any ideas?


I somehow managed to get rid of the error by changing some compiler 
settings and saving them. After this it works again. Maybe the problem 
was due to an VisualD update, which didn't catch a new config format or 
missed something from the old config settings.

-- 
Robert M. Münch
http://www.saphirion.com
smarter | better | faster
Jul 01 2018