feat: link LibUV

[TwoFX]

No description provided.

[ydewit]

It is great to see libuv being integrated into the runtime! May I ask what is the goal? Cross-platform file/network/time IO? Or also non-blocking IO?

[TwoFX]

@ydewit Yes, the ultimate goal is support for non-blocking IO. Note however that this PR only links against LibUV and it might take a very long time until we actually start building anything on top of it, so if you have need for asynchronous IO right now then it probably makes sense to explore alternatives such as lean-libuv for now.

[leanprover-community-mathlib4-bot]

Mathlib CI status (docs):

• ❗ Batteries/Mathlib CI will not be attempted unless your PR branches off the nightly-with-mathlib branch. Try git rebase bcbd7299e94f481c2691c3d4d74f427b44f70968 --onto 7776852d227d4269e34fe30eb51ba0adef90838e. (2024-08-09 07:18:47)
• ❗ Batteries/Mathlib CI will not be attempted unless your PR branches off the nightly-with-mathlib branch. Try git rebase 30a52b794a39256361050c52fe0e41bbff91bc8d --onto dd6ed124baef64a26ef5860f49597fdcef371239. (2024-08-09 15:38:33)

[hargoniX]

We should probably add to the docs page on building Lean that you need to have libuv installed right? Alternatively we could do something similar to the CaDiCal PR and declare libuv as an external project that gets downloaded and compiled by our build system directly.

[TwoFX]

We should probably add to the docs page on building Lean that you need to have libuv installed right? Alternatively we could do something similar to the CaDiCal PR and declare libuv as an external project that gets downloaded and compiled by our build system directly.

Thanks, I've updated the build instructions. We don't want to build libuv as part of our build system, but use either system libraries (when building manually) or take static libraries from Nix (when creating release versions via CI), just as we do it with GMP.