This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Building from source without internet

0

I'm developing on a laptop without internet access. The problem arises when I enter nmake -f Makefile.nmake setup. I fail because it tries to use wget to get the library files from the internet.

I have all the appropriate library files on the laptop without internet, but where do I put them so wireshark can use them? Does anyone have a set of instructions to follow to build wireshark without internet?

This question is marked "community wiki".

asked 09 Aug '11, 11:14

Dean%20Wormer's gravatar image

Dean Wormer
6113
accept rate: 0%


One Answer:

2

During the build process, Wireshark downloads its dependencies to C:\wireshark-win32-libs (assuming you are following the Win32 Step-By-Step instructions). This is the folder in which you should place these files.

answered 09 Aug '11, 12:07

multipleinterfaces's gravatar image

multipleinte...
1.3k152340
accept rate: 12%

So I took the files from http://anonsvn.wireshark.org/wireshark-win32-libs/trunk/packages

In the directory you mention, do I put the .zip files and let nmake -f Makefile.nmake setup take care of it? Do I extract the folders, extract the dlls and just run nmake -f Makefile.nmake all?

Sorry for the noobish questions. I appreciate your help

(09 Aug '11, 12:31) Dean Wormer

placing the .zip archives in the folder and running nmake -f Makefile.nmake should be sufficient. YMMV since building on Windows without directly following the steps in the developer's guide is always a bit tricky.

(09 Aug '11, 12:55) multipleinte...
2

Once you have all the dependency files, go ahead and run nmake -f Makefile.nmake setup, which will run the verify_tools, clean_setup and process_libs targets. When you get to the process_libs part, you'll see messages such as, "File blah.zip already there; not retrieving". You only need to run setup once (unless you want to update any libraries). When the setup completes, you're ready to run nmake -f Makefile.nmake all. If you want to create an installer, you'll need to get other stuff though, such as the NSIS installer and vcredist_x86.exe. See the Win32 guide for more details.

(09 Aug '11, 18:40) cmaynard ♦♦