Wireshark · Wireshark-dev: Re: [Wireshark-dev] Compilation errors while building the Wireshark sources

[Rohan Solanki <solanki.rohan@xxxxxxxxx>]

Ok .. got it!!!!!!!


Thanks Abhik for the reply...

On Thu, Apr 30, 2009 at 5:59 AM, Abhik Sarkar <sarkar.abhik@xxxxxxxxx> wrote:

Hi Rohan,

The distclean target cleans up any files made for a distribution... this removes any generated stuff and keeps the sources untouched.

You can't compile a single file if you are changing the in-built dissectors because all of the functionality is part of one big shared library and that library needs to be relinked. I would like to point out however that the build system "compiles" only changed sources (and a few other files) and only re-links them... so, I normally find that if I change only a particular dissector the re-build takes a only about a minute, but after a distclean it takes a good 5-10 minutes (on my system).

Regards,
Abhik.

On Thu, Apr 30, 2009 at 3:32 PM, Rohan Solanki <solanki.rohan@xxxxxxxxx> wrote:

Hi Abhik,
 
What does distclean does? I want to know will  my changes remain when i do distclean?
And also how do i compile a single file instead of building the whole project?

Thanks in advance
Rohan

On Thu, Apr 30, 2009 at 4:28 AM, Abhik Sarkar <sarkar.abhik@xxxxxxxxx> wrote:

Did you try
nmake -f makefile.nmake distclean
nmake -f makefile.nmake all
This has often worked for me in similar situations.

On Thu, Apr 30, 2009 at 3:08 PM, Anonymous Anonymous <a.master.blaster@xxxxxxxxx> wrote:

No luck so far.
I've re-downloaded the sources using TortoiseSVN and compilation again fails in the exact same place.
Any suggestions?

On Wed, Apr 29, 2009 at 9:14 AM, Jaap Keuter <jaap.keuter@xxxxxxxxx> wrote:

Hi,

Well, he's building the 1.1.4 development version, so 2008 should be fine. It
seems that you've a botched tarball or working copy, since little has changed in
this area for a long time.
Try downloading a new tarball or revert changes in the working copy and start
from the current head of development.

Thanx,
Jaap

Rohan Solanki wrote:
> hi,
>    I think you should try building wireshark with visual studio 2005.
> Also Make appropriate changes in the config.nmake file. I also had
> problems with visual studio 2008. I have successfully build and running
> wireshark 1.0.5 with visual studio 2005.
>
> Rohan.
>
> On Tue, Apr 28, 2009 at 7:19 PM, Anonymous Anonymous

> <a.master.blaster@xxxxxxxxx <mailto:a.master.blaster@xxxxxxxxx>> wrote:
>
>     Hi everyone,
>
>     I'm new to the Wireshark development process and I'm having some
>     building issues I hope you will be able to solve. Ok, so here it comes.
>
>     I've followed the developers manual step-by-step and everything
>     worked out fine until I had to issue the command "name
>     Makefile.namke all". For some unknown reason this command seems to
>     fail over and over again.
>     The relevant output lines I managed to extract from the console are
>     as follows:
>
>     /*dissectors.lib(packet-ncp-sss.obj) : error LNK2001: unresolved
>     external symbol _
>     ett_nds
>     libwireshark.dll : fatal error LNK1120: 1 unresolved externals
>     NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual
>     Studio 9.0\VC\BIN
>     \link.EXE"' : return code '0x460'
>     Stop.
>     NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual
>     Studio 9.0\VC\BIN
>     \nmake.exe"' : return code '0x2'
>     Stop.
>
>     */The same output also appears when I'm trying to build the .sln
>     file provided is the sources using VC++ 2008 Express Edition.
>     Can someone point out what the problem is?
>
>     Thanks in advance. Any help will be deeply appreciated.
>
>     My building environment specs:
>     OS - Microsoft Windows XP SP3
>     IDE - Microsoft Visual C++ 2008 Express Edition
>     SVN - TortoiseSVN
>     Wireshark version - 1.1.4.0 (version info was taken from the
>     config.nmake file)
>

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe