Closed Bug 119610 Opened 24 years ago Closed 19 years ago

Details on compiling with various options (set version info,branding,prefixdir)

Categories

(Developer Documentation Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: bootsy52, Assigned: endico)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:0.9.7+) Gecko/20020111 BuildID: CVS Jan 11th 2002 CET *** PREFACE, I do not want to do this after the build I want to compile ****** this options in **************** I really have search my a** off, to find any documentation leading on how to change the version info for mozilla, this is needed because otherwise 0.9.7 themes will fail for my svg enabled build which is versioned 0.9.7+, so I set this in ################# configure.in MOZILLA_VERSION='0.9.7' ################## Guess, what? I doesn't work, but please I want to change this for the build NOT afterwards. 2. Is it possible to build a standalone Mail and News Mozilla ?? 3. Is it possible to not to build the HTML editor, or better said to let it disappear from the Task Menu ?? As far as I understood the editor is also used for compose messages and so on. 4. How to build a browser standalone Mozilla 5. How to let the menus Debug QA dissapear ?? 6. --with-user-appdir=.mozilla-097 does not work, mozilla still creates .mozilla directory. 7. How to get Mozilla that a gmake -f client.mk end in the prefix defined user dir ?? Does not work for me, --prefix=/usr/lib/mozilla-097 ends despite of prefix flag in dist/bin. OK, that's for now, I would be very very very glad if you could let me know something of the untold features in compiling the source. I coulnd't find any satisfying documentation. And I really want to customize Mozilla at build time. Reproducible: Always Steps to Reproduce: 1. GET MOZILLA from CVS and try to compile Mail only (even News is not needed) 2. Compile the browser only 3. Compile but don't build the editor actuall so that it not appears in the Task menu Actual Results: Unsatisfied that I'm not able to tweak Mozilla that way Expected Results: Better documentation system for advanced options on compiling the source code. Also, the possiblity to build more modular, e.g if I want only the Mail application that I can only build the Mail application I would help coding if I could do C, unfortunatley I can do only Perl
accepting QA for mozilla developer docs. some of these bugs have been around for a _long_ time. Reporters, would you please review the bugs, see if the issues have been resolved, and close bugs appropriately. I will do a full review of all bugs not touched in one week (8th April). Thanks. </spam>
QA Contact: endico → imajes
This bug should probably be closed. It's very old and many of the questions could be solved using the Build Configurator: http://webtools.mozilla.org/build/config.cgi 1) I believe you would compile with --enable-official-branding, and that the version number is set in lxr.mozilla.org/seamonkey/source/config/milestone.txt . However there are NO documents on mozilla.org that mention this file. Perhaps you also need to set the environment variables BUILD_OFFICIAL=1 and/or MOZILLA_OFFICIAL=1? 2) Thunderbird 3) --enable-plaintext-editor-only? 4) Firefox 5) The debug UI is manually remove from branches. This is currently tracked by bug 202315. If you build from a milestone tarball then you won't get these menues. If you don't then you shouldn't set the version number to identify a milestone. 6) That would be a separate bug if it's still the case which I doubt 7) What?
OS: Linux → All
Hardware: PC → All
Several issues in one bug -> invalid. BTW, the documentation is in the wiki now, so you can just make the edits you think need to be done.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Component: Mozilla Developer → Documentation Requests
Product: Documentation → Mozilla Developer Center
Component: Documentation Requests → Documentation
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
You need to log in before you can comment on or make changes to this bug.