[Enigmail] Building Enigmail for TB comm-central: static or shared, libxul or not?

[Patrick Brunschwig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Michael J Gruber wrote:
> Ludwig Hügelschäfer venit, vidit, dixit 01/23/09 20:42:
>> Hi,
>>
>> Michael J Gruber wrote on 23.01.2009 13:56 Uhr:
>>> Hi there,
>>>
>>> I'm trying to build Enigmail for current TB nightlies. (I'm on 64bit
>>> Fedora 10 so I can't run Mozilla's 3.0b1 binaries easily anyways, and
>>> can't used binary Enigmail xpi either).
>>>
>>> I can build and run TB from a hg checkout of comm-central. Yeah ;)
>>>
>>> For building Enigmail (from cvs),
>> Are you using enigmail trunk (aka 0.96a)?
> 
> Yes, that's what I meant by cvs, sorry. A current cvs checkout from trunk.
> 
>>> I've been following the instructions
>>> on the Enigmail website and ended up with the attached error which seems
>>> to be related to a conflict in build options (shared/static).
>>>
>>> I've built TB with "ac_add_options --enable-static --disable-libxul"
>>> because d.m.o. says TB can't be built shared with libxul (and also
>>> because I wanted to "make package"). Is this still true? How
>>> (static/shared/libxul) do you build TB when you build Enigmail for TB 3
>>> nightlies?
>> Sorry, I don't know anything about the building process on linux. In
>> order to build the Mac OS X nightlies, I'm using these options for TB trunk:
>>
>> mk_add_options MOZ_OBJDIR=/path/to/my/objdir
>> ac_add_options --disable-tests
>> ac_add_options --disable-debug
>> ac_add_options --enable-crypto
>> ac_add_options --enable-optimize
>> ac_add_options --enable-static-mail
>> ac_add_options --enable-application=mail
>> mk_add_options MOZ_CO_PROJECT=mail
>> mk_add_options AUTOCONF=autoconf213
>>
>> Maybe you get better help in mozilla.dev.builds on news.mozilla.org.
> 
> I tried those options (they're the ones from enigmail.mozdev.org) minus
> the autoconf. I can build and run TB comm-central successfully with
> these options as well as others.
> 
> My problem is building enigmail, which is why I think I'd better post
> here than on mozilla.dev.builds. So, my questions really are:
> 
> - Which options do you use when you build enigmail.xpi? (probably the
> ones above)

Here are my options:

mk_add_options MOZ_CO_PROJECT=mail
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/enigdev
mk_add_options AUTOCONF=autoconf2.13

ac_add_options --enable-application=mail
ac_add_options --enable-optimize
ac_add_options --disable-debug
ac_add_options --disable-tests
ac_add_options --enable-codesighs
ac_add_options --disable-shared
ac_add_options --enable-static
ac_add_options --disable-update-packaging
ac_add_options --disable-debug
ac_add_options --disable-tests
ac_add_options --enable-codesighs
ac_add_options --disable-shared
ac_add_options --enable-static
ac_add_options --disable-crashreporter

> - Which combination of TB comm-central sha1 and Enigmail cvs rev. is
> known to build and run well together?

any. I create nightly builds and they usually work fine.

- -Patrick

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBSX3A/XcOpHodsOiwAQgErwf8DpGe0aD1mRBMMRtDZbdfDjy4OLY/Q50u
0R7tfooueeh2wn9PoVXaoleR67WlpmFPf+iegT7F5/qKjO88ySVLJg6yPp0OVLAU
kI4vU4/76A5R6p/VW0YTw3Z1eZvNikjDLu1AdEdqc67EIAdMTWaBQ/llmhPZx1/U
Htl6r1rYAcANGCkTH4GLAlxyzq+onRZvpSw1otzExiEAMyJSbeZBZYyBMEl+tKt2
GoGsBly/xJkX6tZ6yLnlIorvY85po5s3dwtUQZcumLZISLJNrtwgddIip4pazYRM
aFBL+rnL0cBy6+G1txZReeYNa2lR8Jy1Ov9irT3F78PKAcso2lacSw==
=BrrU
-----END PGP SIGNATURE-----