Closed Bug 704104 Opened 13 years ago Closed 13 years ago

Investigate building enigmail on our build infrastructure

Categories

(Mozilla Messaging Graveyard :: Release Engineering, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: Usul, Unassigned)

Details

I'm ccing Patrick has he knows what the build requirements are more precisely than I do. Patrick can you explain what your needs are and how enigmail should be built ?
The build instructions for Enigmail are published here: http://enigmail.mozdev.org/download/source.php.html A short summary: 1. create a full Thunderbird build 2. extract the Enigmail source code into .../mailnews/extensions/ 3. run makemake -r from .../mailnews/extensions/enigmail 4. cd to OBJDIR/mailnews/extensions/enigmail 5. run make && make xpi
Sorry, I forgot to add that building Enigmail does not require more than building Thunderbird on any platform.
(In reply to Patrick Brunschwig from comment #1) > The build instructions for Enigmail are published here: > http://enigmail.mozdev.org/download/source.php.html Definitely possible, but since it requires special build steps, somewhat tricky to merge into our build system. Not impossible, just special-casing we try and shy away from. Ideally, figuring out a way that leaves the build system unchanged would be much preferred. > A short summary: > 1. create a full Thunderbird build Any specific build stuff necessary? Debug vs non-debug, etc ? Or should it work with just about any build ? > 2. extract the Enigmail source code into .../mailnews/extensions/ I assume it's in source-controls somewhere ? > 3. run makemake -r from .../mailnews/extensions/enigmail ./makemake -r > 4. cd to OBJDIR/mailnews/extensions/enigmail > 5. run make && make xpi That worked for me, except I got a build time failure: /usr/bin/python2.7 [comm-central]/mozilla/build/xpccheck.py \ [comm-central] \ [comm-central]/mail/test/xpcshell.ini \ [comm-central]/extensions/ipc-pipe/tests/unit Traceback (most recent call last): File "[comm-central]/mozilla/build/xpccheck.py", line 136, in <module> initests = getIniTests(d) File "[comm-central]/mozilla/build/xpccheck.py", line 62, in getIniTests mp.read(os.path.join(testdir, 'xpcshell.ini')) File "[comm-central]/mozilla/build/manifestparser.py", line 442, in read raise IOError('Missing files: %s' % ', '.join(missing)) IOError: Missing files: [comm-central]/extensions/ipc-pipe/tests/unit/xpcshell.ini
(In reply to Philippe M. Chiasson (:gozer) from comment #3) > > > A short summary: > > 1. create a full Thunderbird build > > Any specific build stuff necessary? Debug vs non-debug, etc ? Or should it > work with just about any build ? It should work with any build. Tests are most likely not working (see below). > > 2. extract the Enigmail source code into .../mailnews/extensions/ > > I assume it's in source-controls somewhere ? yes, it's in CVS on mozdev.org: cvs -d :pserver:guest@mozdev.org:/cvs co enigmail/src > > 3. run makemake -r from .../mailnews/extensions/enigmail > > ./makemake -r > > > 4. cd to OBJDIR/mailnews/extensions/enigmail > > 5. run make && make xpi > > That worked for me, except I got a build time failure: > > /usr/bin/python2.7 [comm-central]/mozilla/build/xpccheck.py \ > [comm-central] \ > [comm-central]/mail/test/xpcshell.ini \ > [comm-central]/extensions/ipc-pipe/tests/unit > Traceback (most recent call last): > File "[comm-central]/mozilla/build/xpccheck.py", line 136, in <module> > initests = getIniTests(d) > File "[comm-central]/mozilla/build/xpccheck.py", line 62, in getIniTests > mp.read(os.path.join(testdir, 'xpcshell.ini')) > File "[comm-central]/mozilla/build/manifestparser.py", line 442, in read > raise IOError('Missing files: %s' % ', '.join(missing)) > IOError: Missing files: > [comm-central]/extensions/ipc-pipe/tests/unit/xpcshell.ini Yes, that's the failing tests I mentioned above. I disabled them now in the Makefile (committed to CVS).
Quick update, with the modified code from CVS, I got a successful build and created: enigmail-1.4-linux-x86_64.xpi
I'm working on getting rid of C++ in Enigmail, this is therefore no longer necessary.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.