Nmap Development mailing list archives

RE: Compiling Nmap on Visual C++ 2005 Express


From: "Sina Bahram" <sbahram () nc rr com>
Date: Sun, 27 Nov 2005 23:36:14 -0500

Parden my ignorance, but the only context I've played with cflags in has
been already made makefiles, not those that are going to be dynamically
generated by autoconf.

A few questions:

#1: does VS even honor cflags? I thought this was handled by the solution
properties, and other vs specific features. Also, VS doesn't use autoconf or
make, so how do cflags mean anything in this context?

#2: does one therefore make the appropriate changes in the configure script
or in the makefile.in file?

Thanks much

Take care,
Sina

-----Original Message-----
From: nmap-dev-bounces () insecure org [mailto:nmap-dev-bounces () insecure org]
On Behalf Of Gisle Vanem
Sent: Sunday, November 27, 2005 11:27 PM
To: kx; Sina Bahram
Cc: nmap-dev () insecure org
Subject: Re: Compiling Nmap on Visual C++ 2005 Express

"kx" <kxmail () gmail com> wrote:

I just compiled the new alpha as well.

Seems to be due to the following in pcre.h

/* Win32 uses DLL by default; it needs special stuff for exported 
functions. */

#ifdef _WIN32
#  ifdef PCRE_DEFINITION
#    ifdef DLL_EXPORT
#      define PCRE_DATA_SCOPE __declspec(dllexport)
#    endif
#  else
#    ifndef PCRE_STATIC
#      define PCRE_DATA_SCOPE extern __declspec(dllimport)
#    endif
#  endif
#endif

Which should be:

/* Win32 uses DLL by default; it needs special stuff for exported 
functions. */

/* Removed -- Fyodor */

Just remove those defines and everything should work fine

Or do the obvious; add PCRE_STATIC to the CFLAGS.

--gv



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



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


Current thread: