2009/10/28 Siva S <[email protected]> > Hi, > > If I do "nmake -f makefile.nmake process_libs", then also it was trying > to download the library files. I have given the library files path also. > > Thanks & Regards, > Siva S > > > > Peter Johansson wrote: > > 2009/10/27 Siva S <[email protected]> > >> Hi, >> >> Thanks for your comments. >> If I do nmake -f Makefile.nmake allthen, this is the error I got. >> "ERROR: Package glib_2.18.1-1_win32.zip is needed but is apparently >> not downloaded;" >> I think I have to explicitly configure wireshark with the library >> paths. I was not able to do "nmake -f Makefile.nmake setup" because, I don't >> have a internet connection. So, I downloaded all the library files required >> by wireshark and installed it on "C:/wireshark-win32-libs/". >> Please help me on this. Thanks in advance. >> >> Thanks & Regards, >> Siva S >> >> >> >> Graham Bloice wrote: >> >> Jaap Keuter wrote: >> >> Don't work in cygwin window. Do nmake in 'DOS box' >> >> Send from my iPhone >> >> On 27 okt 2009, at 12:59, Siva S <[email protected]> >> <[email protected]> wrote: >> >> >> >> Hi, >> >> I am trying to install wireshark in windows XP. I have installed >> WinPcap also. I was using cygwin to install wireshark. >> I have added one dissector parser code which is working fine in >> linux. After doing "make distclean" in linux environment, and I have >> taken the same source code to install it in windows machine. >> >> If I am doing ./configure, it was showing the error "error: Can't >> link with library libpcap.". >> Can anybody help me on this?. Please correct me if I was wrong. >> >> -- >> Thanks & Regards, >> Siva >> >> To amplify Japp's advice, Wireshark on Windows is built with the Visual >> Studio toolset using nmake. Cygwin is required, but only for some small >> tools not natively provided on Windows. >> >> Read the Developers Guide on tool setup: >> http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html >> >> -- >> Regards, >> >> Graham Bloice >> >> > Since you downloaded the libraries on your own rather than by "nmake -f > makefile.nmake setup" you most likely also need to edit your config.nmake > file and adjust the WIRESHARK_LIBS to pinpoint to where you downloaded the > libraries. > > Once WIRESHARK_LIBS points to the correct location, you should be able to > run "nmake -f makefile.nmake process_libs" that will then process the > downloaded libraries preparing them for the build > (extracting/decompressing/whatever). > > When that is done, run "nmake -f makefile.nmake verify_tools" to ensure > that nothing else is missing. > > Then (if you passed the steps above), you should be able to compile and > link! > > Regards, Peter > > It only actually attempts to download the library files if you put them in the "wrong location", my guess is that you do not have WIRESHARK_LIBS pointing in the right direction yet.
When I do "nmake -f makefile.nmake process_libs" on my machine I get the following: c:\Wireshark>nmake -f makefile.nmake process_libs Microsoft (R) Program Maintenance Utility Version 8.00.50727.762 Copyright (C) Microsoft Corporation. All rights reserved. ****** glib_2.20.5-1_win32.zip ****** Using Internet Explorer proxy settings. HTTP proxy (proxy.se.abb.com:81) has been specified and will be used. Downloading gtk2.16/glib_2.20.5-1_win32.zip into C:\WIRESH~3, installing into glib File `glib_2.20.5-1_win32.zip' already there; not retrieving. Notice the last line on the "...already there; not retrieving". Regards, Peter
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
