Need to improve build method of embed.jar

RESOLVED WONTFIX

Status

Core Graveyard
Embedding: Packaging
RESOLVED WONTFIX
16 years ago
2 years ago

People

(Reporter: Conrad Carlen (not reading bugmail), Assigned: Conrad Carlen (not reading bugmail))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

16 years ago
Currently, the way that embed.jar gets built is not very flexible, and uses a
pre-made installed-chrome.txt. If an embeddor wants to add or remove things from
this jar, it's difficult.
  About a year ago, Pink did some nice work for the MacPerl driven Mac build.
You could specify which parts of the chrome you wanted in your build prefs and
then, depending on what chrome was packaged, an installed chrome.txt was
dynamically generated. We need to have this nicety in the unified gmake world.
  Once it is flexible enough, we could have a nice README in embedding/config
which gave examples of how to add/remove chrome from the jar.

BTW - can we get an "Embedding: Packaging" bugzilla component?
(Assignee)

Comment 1

15 years ago
Moving to new bugzilla component.
Component: Embedding: GRE Core → Embedding: Packaging
QA Contact: ashishbhatt → carosendahl
QA Contact: carosendahl → packaging

Comment 2

9 years ago
embed.jar is dead
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.