Skip to main content


A full clean rebuild of #curl on my machine takes about 3.5 seconds. If I make it a "unity" build, it can be done in 2.3 seconds.
#curl
in reply to daniel:// stenberg://

is there a reason to not have it as a unity build by default?
Unknown parent

daniel:// stenberg://
@holsta then your laptop is very slow or you do more than what I measured
Unknown parent

daniel:// stenberg://

@dlatchx @holsta

"cmake -DCMAKE_UNITY_BUILD=ON -B build" takes 11.1 seconds for me

"make -sj" in that build dir takes 2.3 seconds for me

but I normally use configure

A very "complete" configure run takes <10 seconds for me and then "make -sj"takes 3.4-3.5 seconds.

This is on a 13th Gen Intel i7-13700K running Linux.

in reply to daniel:// stenberg://

40 seconds for cmake, plus 25 seconds for the build on my build machine
Unknown parent

daniel:// stenberg://
@lanodan @dlatchx @holsta @a1ba only that they did not die. They just shrunk and we normal humans don't use them. They still have users and they still run configure scripts...
Unknown parent

daniel:// stenberg://
@a1ba @dlatchx @holsta @lanodan there is, and we don't do a very good of using that in curl. But then I think I run curl's configure probably more than anyone else anywhere and I don't suffer much...
in reply to daniel:// stenberg://

wish more build systems supported running configure tests in parallel.

Waf does but it's a bit of a hassle to set up.

in reply to 27329ed9-2211-a1ba-9371-e2641bf0dcb6

Or would clean themselves to not transform into a pile of workarounds dedicated to systems that died 20 years ago:utils-std # time ./configure
0m00.19s real 0m00.09s user 0m00.10s system
badwolf # time ./configure
0m00.05s real 0m00.03s user 0m00.03s system
in reply to Haelwenn /элвэн/ :triskell:

I barely remember there was some sort of a cache for typical autotools checks, to save time for modern systems.