Closed Bug 122528 Opened 23 years ago Closed 21 years ago

Nov 2001 SDK required for Printing

Categories

(SeaMonkey :: Build Config, defect, P3)

Product:
SeaMonkey
Component:
Build Config
Platform:
x86
Windows 2000
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX
Milestone:
Future

People

(Reporter: rods, Assigned: granrosebugs)

References

Details
Blocks: 122530
need to figure out what kind of side effects might be presented if we upgrade
the SDK in the release builds.
rod, can you put instructions about how to build with the new SDK here?
The potential side-effect is breaking our builds on older windows platforms, and
(more critically) causing the release binaries to not work (for printing, at
least) on older windows releases (98, NT).
what leaf said.  We need mozilla.org and Netscape Marketing to make the call as
to which is more important - this feature or win98 and NT support.  Netscape
release doesn't have resources to do both since this would mean doubling all our
win32 support hw.
Assignee: granrose → leaf
Priority: -- → P3
Target Milestone: --- → mozilla0.9.9
Rod has informed me that this is, in fact, a runtime detected thing. So we still
only need to make one build happen (newer platforms will have the new print
dialog to take advantage of, older platforms will fall back onto the old dialog).

I think it's safe to just install the new SDK and update the MOZ_VER on the
release machines. I don't think it's ok to *require* the new MOZ_VER for all
windows builds, but i can update the instructions with options for building with
more current windows compilers/sdks.
What is the define we need to set in order to build this fabulous printing 
stuff?

seaquake has the core november 2001 sdk installed, so we just need to flip the 
build switch.
Status: NEW → ASSIGNED
this obviously didn't get turned on; we have to resolve whether we're really
going to make two sets of windows builds.
Target Milestone: mozilla0.9.9 → mozilla1.0
we're not doing two sets of builds.

based on the comments in 122530 I'm assuming this is checked in and this bug
should be closed.
Keywords: nsbeta1
Target Milestone: mozilla1.0 → mozilla1.4final
adt: nsbeta1-
Keywords: nsbeta1 → nsbeta1-
taking and future, until someone figures out what to do with this.
Assignee: leaf → granrose
Status: ASSIGNED → NEW
Target Milestone: mozilla1.4final → Future
engineer gone, wontfix.  if you want it, reopen the bug and reassign it to 
yourself.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WONTFIX
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.