MacArthur, Ian (Leonardo, UK) schrieb:
>>> \FL/Fl_Device.H(216):warning
>> "warning C4273" is easy to find:
>> 
>> https://msdn.microsoft.com/en-us/library/35bhkfb6.aspx
> 
> Well, that's so, but nonetheless I'm not sure that link really helps
> clarify things here, does it?

It tells, that the library overwrites an existing definition. I think
next step would be, to search for this name.

> What I mean is, the OP is linking code (that I presume used to work
> with 1.1.x) and is now getting warnings about dll linkage that were
> not previously present.

But it is a compiler warning and appears before linking, doesn't it? So
I think it is not a conflict of libraries, but a conflict of local
source and a library (as shown in the examples of the link).

> So - is the issue in the way that 1.3.x exports the dll symbols? Or
> is the OP's code doing something that is now "wrong", or is it
> something else?

He should search for all fl_copy_offscreen definitions and then think
about them.

> I'm wondering, in particular, whether the OP has both the 1.1.x and
> 1.3.x FL header files, and his compilation / link phases are picking
> up an incompatible set (i.e. pulling the 1.1 headers and the 1.3
> libs, or v.v.) which probably would trigger mismatches in the
> exported symbols...

This is also a thing, the OP easily can check, because for Visual Studio
he needs to set up all the paths to FLTK by his own. I don't know VS,
but im comparison to gcc it should even print out the paths when
compiling the source.

-- 
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.