Ahhh. We (sqlitebrowser.org) used to do something along those lines in one of our repos too.
We moved to automatically grabbing the SQLite source as a step in our unit tests instead so we always have the latest SQLite release.
One less manual task that needs doing every time there's a new SQLite release.
It turned out to be really easy to do, as the SQLite download page has hidden tags in it just for this purpose:
https://github.com/sqlitebrowser/sqlitebrowser/blob/7a31ef97...
In theory (!) it should be pretty easy to just copy the above code snippet into your unit testing setup, which would also reduce the line count of C code in your repo. :)
In the above code I'd probably use "make -j `nproc`" instead of the hard coded number of cpus (-j2) though, so it automatically uses however many are available. Should probably update that. :)
