Closed Bug 170621 Opened 23 years ago Closed 22 years ago

static build changes for viewer.exe mfcembed.exe and winembed.exe

Categories

(Firefox Build System :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: cathleennscp, Assigned: blythe)

Details

Attachments

(1 file, 2 obsolete files)

Status: NEW → ASSIGNED
Request for r=, sr= Enable static builds for test apps. Fix nsToolkit init problem.
Comment on attachment 105974 [details] [diff] [review] Enable static builds for test apps. so um, if we ever flip over to packaging static builds, the file size is going to quadruple...
Attachment #105974 - Flags: review?(seawood)
Comment on attachment 105974 [details] [diff] [review] Enable static builds for test apps. That entire toplevel Makefile block is wrong. Why do we want to start building viewer in our nighlty builds? Why is the build order only modified for the static builds?
Attachment #105974 - Flags: review?(seawood) → review-
Comment #3: Why do we want to start building viewer in our nighlty builds? This patch does not change when viewer gets built, only how it is linked. If viewer was not previously getting built, this patch should not cause it to get built. Comment #3: Why is the build order only modified for the static builds? Unfortunately, all the linkage dependencies in a static build are not available until the end of the build cycle. If you require further proof, I will provide specifics upon request.
+ifneq (,$(ENABLE_TESTS)$(MOZILLA_OFFICIAL)) So if tests are enabled and/or it's a nightly build, it's going to build viewer & the other test harnesss. Right, static builds require that executables are built last. My point was why bother with the confusing ifdefs and just move the directories to the bottom of the list like we did for gtkembed?
Comment #5, ouch, you are certainly correct and sorry I missed the implications. I took the "ifneq (,$(ENABLE_TESTS)$(MOZILLA_OFFICIAL))" line orignally from mozilla/embedding/Makefile.in as it appeared the embedding tests get built that way in a non static build. Will change, and will apply the gtkembed-like changes as well. thx!
2nd attempt, tries to address concerns raised by cls. Only build test apps at end of build to avoid special cases. Do not enable viewer to be build when official static build. Still questionable on win32 to build mfcembed and winembed for an official static build, but preserved logic found in original mozilla/embedding/Makefile.in Request for r=
Attachment #105974 - Attachment is obsolete: true
Comment on attachment 106043 [details] [diff] [review] Enable static build for test apps. My linux static build broke in viewer attempting to create viewer_gtk. It couldn't find -lxpconnect. Viewer has one of those classic nasty Makefiles. You'll need to add the extra linking options for each of the viewer_{gtk,qt,xlib} targets. Also, in the toplevel Makefile.in, you should have the test apps build after mozilla.
Attachment #106043 - Flags: review-
Sure thing, will fix. thx! garrett
Hopefully the final patch to enable static builds of test apps. Request for r=
Attachment #106043 - Attachment is obsolete: true
Comment on attachment 109495 [details] [diff] [review] Revised patch to fix linux static build of viewer r=cls
Attachment #109495 - Flags: review+
checked in
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Component: XP Miscellany → Build Config
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: