How to build Mozilla like the official binary builds.

I have asked this several times in other forums, but i
have not got any answer, so i try here also.

I want to build Mozilla (the suite) like the official
binary builds that you can downlad from mozilla.org.
My goal is to have a mozilla installed in /usr just
like the distro-version but one that uses fonts like
the official binary version.

I want to do this on Slamd64 (i have tried on Slack too,
but no luck so far). If i just download a binary installer
and install mozilla in /usr/local, i get what i want regarding
the fonts = good ol helvetica for sans-serifs, no blurry
fonts that hurts my eyes. But that is 32-bit. And of course,
having two Mozillas, one 64-bit with fonts i do not like, and
one 32-bit with fonts i like is also a cluttering of my system.
I want to build my own 64-bit installed in /usr that uses
fonts just like an official binary build does.

So, what do i need to change in the part of the buildscript:

BUILD_OFFICIAL=1 MOZILLA_OFFICIAL=1 \
CFLAGS=-fPIC \
../configure --prefix=/usr \
--libdir=/usr/lib64 \
--enable-optimize=-O2 \
--disable-debug \
--with-default-mozilla-five-home=/usr/lib64/mozilla-${VERSION} \
--enable-strip-libs \
--disable-tests \
--disable-short-wchar \
--enable-nspr-autoconf \
--enable-calendar \
--enable-extensions=default,irc \
--enable-crypto \
--disable-xprint \
--without-system-nspr \
--with-system-zlib \
--enable-default-toolkit=gtk2 \
--disable-freetype2 \
--enable-xft

The above is the distro-buildscript, and of course that
works, it build just fine, but it builds a version using
fonts in the way i do not like. I have tried with enabling/
disabling gtk2, gtk, freetype2, xft in many, many different
combinations, but i get obscene amounts of different errors
everytime i change anything on the three last rows.

It may be that something is missing in the system to build
like the official binaries from mozilla.org. But in order
to sort that out, i need to know how the buildscript should
be configured properly for what i want.

Any body here hwo knows?




--
Software is not manufactured, it is something you write and publish.
Keep Europe free from software patents, we do not want censorship
by patent law on written works.

steelneck wrote:
> and install mozilla in /usr/local, i get what i want regarding
> the fonts = good ol helvetica for sans-serifs, no blurry
> fonts that hurts my eyes. But that is 32-bit. And of course,
> having two Mozillas, one 64-bit with fonts i do not like, and
> one 32-bit with fonts i like is also a cluttering of my system.
> I want to build my own 64-bit installed in /usr that uses
> fonts just like an official binary build does.
>

Mozilla already has the ability to use whatever fonts are on your
system, be they good or bad.

If you can't get what you want using the Edit | Preferences |
Appearance | Fonts pulldown, you can try modifying your userContent.css
and userChrome.css files, as discussed here:

http://www.mozilla.org/unix/customizing.html

Chris Sorenson wrote:
> steelneck wrote:
>
>>and install mozilla in /usr/local, i get what i want regarding
>>the fonts = good ol helvetica for sans-serifs, no blurry
>>fonts that hurts my eyes. But that is 32-bit. And of course,
>>having two Mozillas, one 64-bit with fonts i do not like, and
>>one 32-bit with fonts i like is also a cluttering of my system.
>>I want to build my own 64-bit installed in /usr that uses
>>fonts just like an official binary build does.
>>
>
>
> Mozilla already has the ability to use whatever fonts are on your
> system, be they good or bad.
>
> If you can't get what you want using the Edit | Preferences |
> Appearance | Fonts pulldown, you can try modifying your userContent.css
> and userChrome.css files, as discussed here:
>
> http://www.mozilla.org/unix/customizing.html
>

Nope, it does not even help to take both userContent.css and
userChrome.css from the official binary build to be used by
the distro-build, this has to do with mozillas use of xft and
fontconfig that is chosen at compile-time.

I write this from Slack using an official binary build installed
in /usr/local, and that build is using the same *.css files that
Pat's build installed in /usr does, and belive me.. Pat's build
uses blurry TTF, and the official binary build from mozilla.org
uses crystal sharp non TTF fonts that also scales very well.




--
Software is not manufactured, it is something you write and publish.
Keep Europe free from software patents, we do not want censorship
by patent law on written works.

steelneck wrote:
>
> Nope, it does not even help to take both userContent.css and
> userChrome.css from the official binary build to be used by
> the distro-build, this has to do with mozillas use of xft and
> fontconfig that is chosen at compile-time.
>
> I write this from Slack using an official binary build installed
> in /usr/local, and that build is using the same *.css files that
> Pat's build installed in /usr does, and belive me.. Pat's build
> uses blurry TTF, and the official binary build from mozilla.org
> uses crystal sharp non TTF fonts that also scales very well.
>

Hmmmm, that is weird!

Hard to believe it might be a 64 bit problem, but...

I see there a lot of font complaints in the mozilla newsgroups, maybe
you should ask over in mozilla.support.seamonkey or somesuch...

Chris Sorenson wrote:
> steelneck wrote:
>
>>Nope, it does not even help to take both userContent.css and
>>userChrome.css from the official binary build to be used by
>>the distro-build, this has to do with mozillas use of xft and
>>fontconfig that is chosen at compile-time.
>>
>>I write this from Slack using an official binary build installed
>>in /usr/local, and that build is using the same *.css files that
>>Pat's build installed in /usr does, and belive me.. Pat's build
>>uses blurry TTF, and the official binary build from mozilla.org
>>uses crystal sharp non TTF fonts that also scales very well.
>>
>
>
> Hmmmm, that is weird!
>
> Hard to believe it might be a 64 bit problem, but...
>
> I see there a lot of font complaints in the mozilla newsgroups, maybe
> you should ask over in mozilla.support.seamonkey or somesuch...
>

I have got my answer in the NG mozilla.dev.builds
(also got same answer in mozilla.support.mozilla-suite)

about:buildconfig reports all the config. arguments
that was used to build it. So the official binary is
built with:

--enable-extensions=default,irc,tasks,negotiateauth --disable-tests
--disable-debug '--enable-optimize=-O2 -gstabs+' --without-system-nspr
--without-system-zlib --without-system-jpeg --without-system-png
--without-system-mng --without-system-mng --enable-crypto


I have tried this earlier with a lot of errors, but now
i know this to be correct, so i have to work from there
and try to sort out whats missing. I do not either think
it is a 64-bit problem, it does not compile with that in
ordinary Slack either. Maybe i can find time for some
testing tomorrow..




--
Software is not manufactured, it is something you write and publish.
Keep Europe free from software patents, we do not want censorship
by patent law on written works.