On Nov 16, 2013, at 1:54 AM, [email protected] wrote:
> The Buildbot has detected a new failure on builder Windows-7-x64 while
> building Wireshark (development).
> Full details are available at:
> http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds/7888
>
> Buildbot URL: http://buildbot.wireshark.org/trunk/
>
> Buildslave for this Build: windows-7-x64
>
> Build Reason: scheduler
> Build Source Stamp: 53366
> Blamelist: darkjames
>
> BUILD FAILED: failed nmake all
Would somebody with sufficient Windows build experience care to indicate what
the right way is to handle a variable (not a function) that is:
exported by library A;
imported by library B;
declared in a header file that's included by the source file in library
A that defines the variable and by the source files in library B that use the
variable?
The problem is that the source file in library A *and* the source files in
library B are *both* compiled with "this is going into a DLL" flag on Windows,
as they *are* all going into DLLs on Windows, so that -D flag cannot be used to
control whether the declaration in the header file is "this is being exported"
(__declspec(dllexport)) and "this is being imported" (__declspec(dllimport)).
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <[email protected]>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:[email protected]?subject=unsubscribe
