Nmap Development mailing list archives

RE: Nmap 4.03 Released; Survey Status


From: "Scott Worley" <smw () pobox com>
Date: Tue, 25 Apr 2006 00:00:21 -0400

I was able to compile with Visual Studio 2005 command line (build log
Attached for those interested).  I am using Visual Studio 2005, so I needed
to convert the current .sln to the 2005 format first.  To do this command
line, you will also need to ensure that the path for devenv.exe is in your
profile.

Also, my understanding is that this should be possible via .NET framework
(meaning Visual Studio should not be required to build from source, however
I have not tried this here at home or at work ... May be something fun to
try out, I will reply again if I am able to get it to fly)

Path Update:
1.  select -> My Computer (right click) -> Properties -> [Advanced Tab] ->
Environment Variables -> System variables.
2.  Scroll down to Path.
3.  Add to the beginning of the Path: C:\Program Files\Microsoft Visual
Studio 8\Common7\IDE;
4.  Select -> OK

Solution Conversion to 2005:
1.  Open the nmap-4.03\mswin32\nmap.sln file (double click)
2.  Message stating solution must be converted, bla, bla, bla.  Select Next
(or Finish to skip the next two questions).
3.  Message asking if you want to create a backup?  Select Next (assuming
the default of yes is sufficient).
4.  Select Finish.  (Noting that there are warnings on the conversion,
however all files converted).
5.  Select Close.
6.  Close Visual Studio.
7.  Select Yes to save your changes.

Instruction Update:  Assuming your environment has access to DevEnv.

   1.      Download the latest Nmap source distribution from
http://www.insecure.org/nmap/download.html. It has the name
nmap-version.tar.bz2 or nmap-version.tgz . Those are the same tar file
compressed using gzip or bzip2, respectively. The Bzip2-compressed version
is smaller.
   2.      Uncompress the source code file you just downloaded. Recent
releases of the free Cygwin distribution can handle both the .tar.bz2 and
.tgz. Use the command tar xvjf nmap-version.tar.bz2 or tar xvzf
nmap-version.tgz, respectively. Alternatively, the common Winzip application
can decompress the .tgz version.
   3.      Open the command prompt.  Start -> Run -> cmd.
   4.      Change your directory to where you decompressed nmap.  "cd
c:\temp".
   5.      Run devenv against the nmap.sln file.  "devenv
nmap-4.03\mswin32\nmap.sln /build release >> buildlog.out"  Use Debug
instead if you are trying to debug a problem with Nmap.
   6.      The executable and data files can be found in
map-VERSION/mswin32/Release/ (or Debug). You can copy them to a preferred
directory as long as they are all kept together.
   7.      Instructions for executing your compiled Nmap are the same as
given previously for the .zip binaries. Take special note of the WinPcap
requirement.

I hope this helps ..??..

BTW:  I ran a quick smoke test on the new nmap.exe and all appears well.

Scott Worley
smw () pobox com

-----Original Message-----
From: nmap-hackers-bounces () insecure org
[mailto:nmap-hackers-bounces () insecure org] On Behalf Of Fyodor
Sent: Monday, April 24, 2006 2:20 PM
To: nmap-hackers () insecure org
Subject: Nmap 4.03 Released; Survey Status

Hello everyone,
-----snip-----snip-----
o Improved the Windows build system -- mswin32/Makefile now takes care
  of packaging Nmap and creating the installers once Visual Studio (GUI)
  is done building the Release version of mswin32/nmap.sln.  If someone
  knows how to do this (build) step on the command line (using the
  Makefile), please let me know.  Or if you know how to at least make
  'Release' (rather than Debug) the default configuration, that would be
  valuable.
-----snip-----snip-----
Cheers,
Fyodor


_______________________________________________
Sent through the nmap-hackers mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-hackers



_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev

Current thread: