476085 - Rename the WIN95 build configuration, in NSPR

Status: RESOLVED WONTFIX

(NSPR :: NSPR, defect)

Description

[Wan-Teh Chang]

In NSPR 4.8 we will drop support of Windows 9x.
It's time to rename the WIN95 build configuration,
which has been a source of confusion.

How about "WIN32"?

Comment 1

[Julien Pierre]

Wan-Teh,

WIN32 sounds good, but it's not very clear what differentiates it from the WINNT build configuration.

We might want to rename the WINNT build configuration, or at least add an alias for it, since NT hasn't been a product in a very long time. Maybe WIN32PLUS, or WIN32EXTENDED ?

Comment 2

[Wan-Teh Chang]

Perhaps we can rename the WINNT build configuration WIN32mxn,
to indicate that it uses the two-level MxN thread model.

Comment 3

[Nelson Bolyard (seldom reads bugmail)]

WinNT -> WinFiber?

Comment 4

[Kai Engert [:KaiE:]]

Whatever is being made here for NSPR should probably be synchronized with NSS.

In NSS, the default has been changed to WIN95 (bug 947652).

What's the current default used in NSPR?

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee didn't login in Bugzilla in the last 7 months.
:KaiE, could you have a look please?
For more information, please visit auto_nag documentation.

Comment 6

[Kai Engert [:KaiE:]]

I think everywhere we're using WIN95 as the default.

I think it would be confusing to have everyone require that they change their build scripts to use a new value, it seems unnecessary to do this.