Wireshark mailing list archives
Re: Compiling Wireshark for Win32
From: Alex Lindberg <alindber () yahoo com>
Date: Thu, 11 Aug 2011 09:06:40 -0700 (PDT)
The correct command is nmake -f Makefile.nmake wireshark.bsc --- On Thu, 8/11/11, news.gmane.com <AndreasSander1 () gmx net> wrote: From: news.gmane.com <AndreasSander1 () gmx net> Subject: Re: [Wireshark-dev] Compiling Wireshark for Win32 To: wireshark-dev () wireshark org Date: Thursday, August 11, 2011, 8:15 AM Alex, thanks for reply. You're right, these compile flags cause the compiler to generate the file. If you would read my mail, you would see, that build always fails. So your "after you build wireshark" assumption doesn't meet. Thanks for suggesting nmake -f Makefile.bsc I am not sure if this would help debugging, but when I invoke this command I get: NMAKE : fatal error U1073: don't know how to make '*.sbr' probably related to the first problem. -- Andy "Alex Lindberg" <alindber () yahoo com> wrote in message news:1313066367.67831.YahooMailClassic () web162007 mail bf1 yahoo com... If you are interested in debugging in a windows environment you can add the compile flags in config.nmake on the LOCAL_CFLAGS variable.: /FR to create .sbr files /Zi to create .pdb files After you build wireshark, you can also do nmake -f Makfile.nmake wireshark.bsc to create the necessary files that will allow your debugger to find the source files. Alex Lindberg --- On Thu, 8/11/11, news.gmane.com <AndreasSander1 () gmx net> wrote: From: news.gmane.com <AndreasSander1 () gmx net> Subject: Re: [Wireshark-dev] Compiling Wireshark for Win32 To: wireshark-dev () wireshark org Date: Thursday, August 11, 2011, 4:28 AM "Stig Bjørlykke" <stig-Koulc05nefLNLxjTenLetw () public gmane org> wrote in message news:CANoXo1QNRsjQq39xqEYW+W3vNib0OxV5bJCbZ0H15CJKuBnGZw-JsoAwUIsXosN+BqQ9rBEUg () public gmane org...
I am a bit surprised about a problem with compiling Wireshark 1.6.0 with
Visual Studio 2005 for Win32.
Why do you
build 1.6.0 when we have released 1.6.1?
The issues you have
are fixed in 1.6.1. I don't want to build 1.6.x at all. I want to upgrade all my dissectors for propriary protocols to Wireshark 1.6. Since there are no PDB files for 1.6.0 (found only for 1.7 at http://www.wireshark.org/download/automated/win32/) and no import library files I need compile Wireshark with all that CygWin, Python, ... installation. Since the ABI should not change in the "stable branch" I should be able to compile to any version as long as I only need a set of files to build a dissector DLL and to debug the DLL in Wireshark. *All I need is:* - libwireshark.lib - all PDB files - all header files (these can be retrieved using SVN) Should I expect that Wireshark source doesn't get through the supported compiler? I know that there are bugs in any software, but usually a change in the last part of the version number indicates a bugfix in the implementation. Okay, I follow your suggestiong, compiling 1.6.1.... Linking libwireshark.dll link /INCREMENTAL:NO /NOLOGO ......... Creating library libwireshark.lib and object libwireshark.exp GeoIP.lib(GeoIP.obj) : fatal error LNK1103: debugging information corrupt; recompile module BTW: The GeoIP-1.4.6-win32ws.zip has been downloaded during this try of build. -- Andy -----Inline Attachment Follows----- ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe -----Inline Attachment Follows----- ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Compiling Wireshark for Win32 news.gmane.com (Aug 10)
- Re: Compiling Wireshark for Win32 Graham Bloice (Aug 10)
- Re: Compiling Wireshark for Win32 Guy Harris (Aug 10)
- Re: Compiling Wireshark for Win32 Graham Bloice (Aug 10)
- Re: Compiling Wireshark for Win32 news.gmane.com (Aug 11)
- Re: Compiling Wireshark for Win32 Stig Bjørlykke (Aug 11)
- Re: Compiling Wireshark for Win32 news.gmane.com (Aug 11)
- Re: Compiling Wireshark for Win32 Alex Lindberg (Aug 11)
- Re: Compiling Wireshark for Win32 news.gmane.com (Aug 11)
- Re: Compiling Wireshark for Win32 Alex Lindberg (Aug 11)
- Re: Compiling Wireshark for Win32 Graham Bloice (Aug 11)
- Re: Compiling Wireshark for Win32 news.gmane.com (Aug 11)
- Re: Compiling Wireshark for Win32 Gerald Combs (Aug 11)
- Re: Compiling Wireshark for Win32 Jeff Morriss (Aug 11)
- Re: Compiling Wireshark for Win32 Gerald Combs (Aug 15)
- Re: Compiling Wireshark for Win32 Helge Kruse (Aug 12)
- Re: Compiling Wireshark for Win32 Gisle Vanem (Aug 12)
- Re: Compiling Wireshark for Win32 Helge Kruse (Aug 12)
- Re: Compiling Wireshark for Win32 Gerald Combs (Aug 15)
- Re: Compiling Wireshark for Win32 Helge Kruse (Aug 15)
- Re: Compiling Wireshark for Win32 Gerald Combs (Aug 16)