Closed
Bug 192274
Opened 23 years ago
Closed 17 years ago
need readme.txt in xpinstall's builder dir
Categories
(SeaMonkey :: Installer, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: ssu0262, Assigned: ssu0262)
Details
A readme.txt is needed in xpinstall/wizard/windows/builder dir to talk about how
the moz installer build process works.
Comment 1•23 years ago
|
||
Yes. There is one, but it is too short.
Stumble blocks:
- shell to use (DOS-prompt or cygwin)
- env vars to set, what they are supposed to be set to
- drive letters or unix paths (in cygwin)
- ../mozilla/ or its parent
- \ or /
- trailing slash or not
- build scripts to run and their required params, with values (same as above)
- prerequirements
- installed software
- which source dirs to build first
- I had to manually build nsztool and nsinstall, I think
- any open, known bugs which users are likely to run into
All that with examples.
Comment 2•23 years ago
|
||
IIRC, I had to:
- Do usual build foo until you have a working build in dist/bin/
- Use DOS-prompt
- Use cygwin (first perl in path).
If using the 1.0 branch, apply patch in bug 173122.
- cd xpinstall/wizard/windows/; make
- cd xpinstall/wizard/windows/nsztool/; make
- cd xpinstall/wizard/windows/nsinstall/; make
- cd xpinstall/wizard/windows/builder/
- set MOZ_SRC=f:\mozsrc\beonex\mozilla\
- perl build.pl -topsrcdir f:\mozsrc\beonex\mozilla
- get your package from dist/install/
Comment 3•23 years ago
|
||
- If tit fails to build a few components, just start the build script again, it
might work the 2. time. (strange)
Updated•23 years ago
|
QA Contact: bugzilla → gbush
Updated•21 years ago
|
Product: Browser → Seamonkey
Comment 4•17 years ago
|
||
Seamonkey and Firefox are using a new NSIS based installer. resolving this old
bug, please reopen if you still get this with the new installer
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•