How to get an error instead of just warning LNK4006 "... already defined in ... second definition ignored"?

Question

When building a static library which contains duplicate definition of a function, MSVC++ 2013 gives me just a warning:

LNK4006 "... already defined in ... second definition ignored"?

I'm afraid that a warning is too easy to miss. Is it possible to make MSVC++ 2013 to report an error and fail the build if multiple definitions for the same function is found (in different .cpp files)?

Note that the reverse of the solution suggested here (i.e. Project Settings > linker > uncheck 'Force file output') is not applicable because that's for an executable, but in this question a static library is in focus thus no "linker" project option.

@Rakete1111, thanks, I thought this option is only available for C/C++ compiler, but not for linker or librarian. — Serge Rogatch, Aug 28 '16 at 08:06
Actually, I thought this also for linker warnings, but now I'm not sure :/ — Rakete1111, Aug 28 '16 at 08:11
@Rakete1111, there are separate "treat warnings as errors" for linker and librarian under Project Properties (as well as for compiler). You can post this as an answer. — Serge Rogatch, Aug 28 '16 at 09:05

score 1 · Accepted Answer · answered Aug 28 '16 at 09:14

1

There doesn't seem to be a way to treat specific warnings as errors. You can however treat every linker warning as error:

Go to: Project Properties -> Linker -> General -> Treat Linker Warnings As Errors and switch it to Yes (/WX).

answered Aug 28 '16 at 09:14

Rakete1111

47,013
16
123
162

How to get an error instead of just warning LNK4006 "... already defined in ... second definition ignored"?

1 Answers1