• DanielG (6/6) Aug 08 2019 "warning LNK4255: library contain multiple objects of the same
• DanielG (1/1) Aug 08 2019 (Maybe I should add: this is on DMD 2.086.0, Windows 10)
• Dukc (4/10) Aug 10 2019 Let me guess, you're linking Vibe.D? I get those errors all the
• DanielG (6/9) Aug 10 2019 No, this is mostly with own code with I believe just one

DanielG <simpletangent gmail.com> writes:

"warning LNK4255: library contain multiple objects of the same 
name; linking object as if no debug info"

Is there some way to get more detail about this warning? Might 
help to know which objects ...

My program is working fine now, but is this going to cause 
problems later on? Like when I want to debug?

DanielG <simpletangent gmail.com> writes:

(Maybe I should add: this is on DMD 2.086.0, Windows 10)

Dukc <ajieskola gmail.com> writes:

On Thursday, 8 August 2019 at 18:14:22 UTC, DanielG wrote:
 "warning LNK4255: library contain multiple objects of the same 
 name; linking object as if no debug info"

 Is there some way to get more detail about this warning? Might 
 help to know which objects ...

 My program is working fine now, but is this going to cause 
 problems later on? Like when I want to debug?

Let me guess, you're linking Vibe.D? I get those errors all the 
time while using it. Haven't noticed effect on behaviour but it 
might be related to why it won't compile as 32-bit.

DanielG <simpletangent gmail.com> writes:

On Saturday, 10 August 2019 at 13:08:39 UTC, Dukc wrote:
 Let me guess, you're linking Vibe.D? I get those errors all the 
 time while using it. Haven't noticed effect on behaviour but it 
 might be related to why it won't compile as 32-bit.

No, this is mostly with own code with I believe just one 
dependency (automem). Seems to work in both x86_mscoff and x86_64 
(aside from the warning).

But yeah, when googling this warning, all I found was people 
talking about it in the context of Vibe.D.