Martin Mathieson wrote:
I checked this in earlier today, but have the following remaining
Windows warning/error.
packet-wimaxasncp.c(4151) : error C2099: initializer is not a constant
This has happened before:
http://www.wireshark.org/lists/wireshark-dev/200702/msg00500.html
but I didn't see anything in the thread that came to a conclusion; my
suspicion:
http://www.wireshark.org/lists/wireshark-dev/200702/msg00505.html
is that "Windows' run-time linker (or whatever the code that implements
DLLs at run time is called) can't resolve a data reference from a
run-time-loaded DLL (a plugin) to a data item from a DLL loaded as a
library, so that the compiler can't generate code with the appropriate
relocation information for that item", but "I'm not enough of an expert
on Windows' run-time linker to say whether that's the case or not".
Does anybody out there know whether a DLL can import a data item from
another DLL? (Not an application importing data from a DLL, and not a
DLL using data from itself, and not a DLL importing a data item from the
application itself - a run-time-loaded DLL picking up a data item from a
startup-time-loaded DLL with which the run-time-loaded DLL could be linked.)
It's certainly possible with the dynamic linking mechanisms used in
various UN*Xes; is it possible in Windows?
