.mozconfig differences; instructions versus official tarball

Talk about code development, features, specific bugs, enhancements, patches, and similar things.
Forum rules
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.

This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.

Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
Walter Dnes
Astronaut
Astronaut
Posts: 714
Joined: 2015-07-30, 20:29
Location: Vaughan, ON, Canada

.mozconfig differences; instructions versus official tarball

Post by Walter Dnes » 2024-10-23, 06:09

I noticed something whilst checking an anomaly on my custom build. I assumed that the .mozconfig at the instruction webpage ( https://developer.palemoon.org/build/linux/ ) would be official. However, it seems to differ slightly from the output of about:buildconfig from the official tarball downloaded from the palemoon.org website (33.4.0.1 64-bit GTK2)

1) The instruction webpage has "--enable-devtools". This does not show up in "about:buildconfig" output from the official tarball.

2) The instruction webpage has "--disable-debug". "about:buildconfig" from the official tarball shows "--disable-debug-symbols".

Features, or bugs, or insignificant?
There are 2 kinds of people in this world...
1) Those who can extrapolate from incomplete data

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 38378
Joined: 2011-08-28, 17:27
Location: Motala, SE

Re: .mozconfig differences; instructions versus official tarball

Post by Moonchild » 2024-10-23, 07:31

We do occasionally change our build config for official builds that aren't necessarily reflected in the build instructions.
That said, any significant changes would show up (if we remember to update the documentation), and what you've seen is insignificant. "enable devtools" is default so the .mozconfig for it is redundant and doesn't do anything.
Same for "disable debug".

The disable-debug-symbols is only important for debugging runtime-errors/attaching a debugger. I believe this has considerable impact on resulting binary sizes on Linux, but memory is a bit hazy as to why it's included in our builds.
"There is no point in arguing with an idiot, because then you're both idiots." - Anonymous
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
andyprough
Board Warrior
Board Warrior
Posts: 1179
Joined: 2020-05-31, 04:33

Re: .mozconfig differences; instructions versus official tarball

Post by andyprough » 2024-10-23, 10:19

Moonchild wrote:
2024-10-23, 07:31
memory is a bit hazy as to why it's included in our builds
Probably in this thread: viewtopic.php?t=28254