Re: [Wireshark-dev] Using DISSECTOR_SUPPORT_SRC

2010-03-22 Thread Jeremy O'Brien
Alright, this will help. However it seems as though wireshark isn't even trying to build my file. As I said, I added it to the DISSECTOR_SUPPORT_SRC array in my Makefile.common, and reconfigured and all that jazz, but wireshark doesn't touch it. Clearly I have missed something else. On Sat, Mar

Re: [Wireshark-dev] Using DISSECTOR_SUPPORT_SRC

2010-03-22 Thread Jeremy O'Brien
Figured it out. Didn't have a \ at the end of the DISSECTOR_SUPPORT_SRC = line, and had to add {$DISSECTOR_SUPPORT_SRC} to my dissector_la_SOURCES line. On Mon, Mar 22, 2010 at 10:18, Jeremy O'Brien obrien6...@gmail.com wrote: Alright, this will help. However it seems as though wireshark isn't

[Wireshark-dev] Using DISSECTOR_SUPPORT_SRC

2010-03-19 Thread Jeremy O'Brien
Hello, I have a perfectly working dissector, but I wanted to move a very large struct I have in it into its own C file. So I moved it (still keeping it static), declared an extern to it in the original file, and added the new c file to DISSECTOR_SUPPORT_SRC in Makefile.common in my plugin's

Re: [Wireshark-dev] Using DISSECTOR_SUPPORT_SRC

2010-03-19 Thread Bill Meier
Jeremy O'Brien wrote: Hello, I have a perfectly working dissector, but I wanted to move a very large struct I have in it into its own C file. So I moved it (still keeping it static), Bingo ! (iow: keeping it not global) declared an extern to it in the original file, and added the new c

Re: [Wireshark-dev] Using DISSECTOR_SUPPORT_SRC

2010-03-19 Thread Jaap Keuter
Hi, Jeremy O'Brien wrote: Hello, I have a perfectly working dissector, but I wanted to move a very large struct I have in it into its own C file. So I moved it (still keeping it static) Keeping it module static? Then there's no visibility outside the module, hence you can't link to it.

Re: [Wireshark-dev] Using DISSECTOR_SUPPORT_SRC

2010-03-19 Thread Sourabh Rathor
I think the problem is that you are trying to extern a static variable. Static variable has a scope in its own file and can't be accessed anywhere else... On Sat, Mar 20, 2010 at 1:13 AM, Jeremy O'Brien obrien6...@gmail.comwrote: Hello, I have a perfectly working dissector, but I wanted to