[Enigmail] Building Enigmail for TB comm-central: static or shared, libxul or not?
Michael J Gruber
michaeljgruber+mozdevnews at fastmail.fm
Mon Jan 26 04:32:45 PST 2009
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)
- Which combination of TB comm-central sha1 and Enigmail cvs rev. is
known to build and run well together?
I just want to make sure I use a known good combination for trying to
build my 64bit xpi.
Michael
More information about the Enigmail
mailing list