Closed Bug 203811 Opened 21 years ago Closed 16 years ago

Need README describing various embedding packages

Categories

(Firefox Build System :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: granrosebugs, Unassigned)

Details

(since my last attempt apparently failed)

We need to document what the various embedding packages available on mozilla.org
are, either on the web site or the ftp server.  From earlier email:

 >>embed-win32.zip
A zip file which has the "base embedding distribution" i.e. the minimal set of
files required to run a client (such as MfcEmbed) which embeds Gecko. No
installer involved here. One just unzips and runs MfcEmbed.

>> gre-win32-installer.exe
Windows standalone GRE installer, which installs a specific version of a GRE.
This installer is used by the GRE enabled Mozilla/NS installers. Also, used by
MfcEmbed installer, please see below

>>mfcembed-win32-installer.exe
An installer which installs the GRE enabled MfcEmbed application. This installer
also contains the standalone GRE installer.The MfcEmbed installer will install a
GRE(by running the GRE installer) if one is not already present on the users
system. It skips the GRE installer part if it finds a compatible GRE already
installed on the users system

>> gecko-sdk-win32.zip
I _think_ this zip file has just the Gecko interfaces which are currently marked
as FROZEN. If that's the case, no, it's not a complete embedable gecko SDK. Doug?
Still needed?
Component: Mozilla Developer → Documentation Requests
Product: Documentation → Mozilla Developer Center
Assignee: endico → nobody
QA Contact: imajes → doc-request
This doesn't really belong in the MDC product.
Component: Documentation Requests → Build Config
Product: Mozilla Developer Center → Core
QA Contact: doc-request → build-config
I think MDC has this covered, and most of those packages no longer exist anyway.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.