As a follow-on from the meson threads, I've done some more testing
with cmake packages.
AFAICS, there are no issues with using -DCMAKE_BUILD_TYPE=Release in
released cmake packages on modern hardware (force -O3 and -DNDEBUG).
One package which I thought might be interesting was x265 (although
I doubt I have anything that needs that codec ;)
On my haswell i7, using just 4 cores, the differences in elapsed
time were just noise, and the space was a consistent 34 MB source
and 14 MB installed (total 47 MB) both for the unoptimized default
build, and the release build.
On this occasion, I then tried using -G Ninja in cmake on the
release build, but the time and space were unchanged (technically,
about 3 seconds faster, but still roundingg to 1.0 SBU, and
identical reports from du -sch).
For the future, I intend to use release builds in my own scripts as
I alter them, and I will probably use ninja for any cmake packages I
edit (although only bigger packages than this really benefit).
ĸen
--
It is said that there are two great unsolved problems in computer
science: naming, cache invalidation, and off-by-one errors.
-- Ben Bullock
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
