Wireshark-dev: Re: [Wireshark-dev] libwireshark.lib is missing someproto_registrar_* methods
From: "Jim Young" <[email protected]>
Date: Wed, 16 Feb 2011 13:22:04 -0500
>Stephen Fisher <[email protected]> 02/16/11 11:57 AM >>>
>> . On Tue, Feb 15, 2011 at 07:57:09PM +0100, Andreas wrote:
>> This might be easy. If all .obj files that are linked in the directory 
>> epan you can do
>> 
>>    cd epan
>>    dumpbin /symbols *.obj | find /v "UNDEF" | find "External"

> [email protected]:/usr/local/src/wireshark>cd epan
> [email protected]:/usr/local/src/wireshark/epan>dumpbin /symbols *.obj | 
> find /v "UNDEF" | find "External"
> dumpbin: No match.
> find: /v: No such file or directory
> find: UNDEF: No such file or directory
> find: External: No such file or directory
> 
> Was that for use on a Linux system?  I run FreeBSD.  Wireshark is meant 
> to compile on many types of Unix.

I think "find" in this context is the Window's "find.exe" (typically 
located C:\WINDOWS\SYSTEM32).   This is Microsoft's 
implementation of grep....

> C:\>find /?
> Searches for a text string in a file or files.
> 
> FIND [/V] [/C] [/N] [/I] [/OFF[LINE]] "string" [[drive:][path]filename[ ...]]
> 
>   /V         Displays all lines NOT containing the specified string.
>   /C         Displays only the count of lines containing the string.
>   /N         Displays line numbers with the displayed lines.
>   /I         Ignores the case of characters when searching for the string.
>   /OFF[LINE] Do not skip files with offline attribute set.
>   "string"   Specifies the text string to find.
>   [drive:][path]filename
>              Specifies a file or files to search.
> 
> If a path is not specified, FIND searches the text typed at the prompt
> or piped from another command.
> 
> C:\>

Best regards,

Jim Y.