Re: [ANNOUNCE] NSPR 4.7.2 Release

"Wan-Teh Chang" <[email protected]> Thu, 30 Oct 2008 10:22:35 -0700
Newsgroups gmane.comp.mozilla.devel.nspr
Message-ID <[email protected]>
On Thu, Oct 30, 2008 at 7:06 AM, Joachim Ziegler <[email protected]> wrote:
>
> I have problems compiling this under Windows with CygWin.
>
> I've followed the steps as given on
>
> https://developer.mozilla.org/en/Checkout_and_Build_NSPR
>
[...]
> So I did
>
> $ mkdir target
> $ cd target
> $ ../mozilla/nsprpub/configure
> $ make
>
> It seems that it does not find "nsinstall":

Yes, you need to download "nsinstall".  It is in the bin directory in the
moztools-static package:
http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/moztools-static.zip

> BTW, the section also mentions a "Classic" way to build under Windows. does
> this mean that building with CygWin only works for the CygWin layer? And to
> build the generic (?) Win32 debug targets, you should issue
>
> gmake OS_TARGET=WIN95
>
> Where does this gmake come from, if it is a classic/native way to compile
> under Windows?

The "Classic" way to build is used for NSPR 4.1.x and earlier.
"Autoconf" is used for NSPR 4.2 and later.  This is stated at
the top of the wiki page.  Because of your question, I just updated
the wiki page to repeat this info.

NSPR uses Cygwin only in the build system.  NSPR's C code
is a native Win32 implementation and is not layered on top of
Cygwin.

"gmake" means GNU make.  It is named "make" in Cygwin and
Linux.  In many Unix systems, "make" is the original make program,
so GNU make is typically named "gmake" or "gnumake" to avoid
name conflict.

> BTw2: How can I create static libraries against which I can link statically?

NSPR build process produces static libraries, but they are not
supported.

Wan-Teh