Contributed 3rd Party Builds • Re: Pale Moon x86-64 SSE2/AVX2

Instead of waiting, I went and ran the build myself, buuut, the version still reads 34.2.0 like from the last time, though it recompiled a bunch of files and took half the time it normally does. Build system bug? Better to delete objdir and get it to recompile everything?

Or what do self-builders do?

FWIW, NSS library version reads like written in the changelog.

My recommended strategy is something like this, assuming you're like me and don't pick a custom name for your objdir:

CODE:

cd Pale-Moon

(go to the directory you cloned Pale Moon into). 2.

CODE:

rm -rf obj*

(I don't trust ./mach clobber, it's burned me before) 3.

CODE:

rm platform/old-configure && rm platform/js/src/old-configure

(Make 100% sure old-configure is regenerated from the .in file, shouldn't be needed but again, I've been burned before) 4.

CODE:

git pull

(Make sure you have the latest changes) 5.

CODE:

git checkout 34.2.2_Release

(Ensures the version pointer is setup correctly, otherwise you'll either get an outdated one or one indicating an alpha) 6.

CODE:

git submodule update

(Ensures the platform is at the right commit for that release of Pale Moon, without you having to dig around in platform manually) 7.

CODE:

./mach build

CODE:

./mach run