Now that BinaryBuilder.jl is picking up steam, I think we can simplify our CI infrastructure a little bit by building dependencies such as LLVM, OpenBLAS, etc... offline for all the systems we care about, then at CI time, just downloading the relevant tarballs, extracting them into usr
and continuing the build. I think using prebuilt binaries for these large chunks will significantly simplify our build process, and should help make CI more reliable and easier to iterate on.
The deps we could prebuild (and their status if someone's already started building it) are:
As I continue to build pieces of the ecosystem, I'll update this list.
This can be done piecemeal, right? I.e. use prebuilt binaries for the things where they exist while we continue to build dependencies from source for the rest.
BinaryBuilder will need https://github.com/JuliaPackaging/BinaryBuilder.jl/issues/32 before we can use it with our full CI infrastructure here.
I updated the list above. If this is the way forward, I can put together a few more of the Base dependencies.
Also, perhaps for some of the simpler dependencies, we should start using BinaryBuilder already rather than waiting for everything.
Yes, I don't understand why we would wait for everything here. It seems far better to start using BinaryBuilder for the dependencies for which it's available. We also do __NOT__ have to wait for FreeBSD to do this: we can use BinaryBuilder on some platforms and not others.
Not using it everywhere only doubles the workload though.
Workload on what?
Having to maintain a build process on BinaryBuilder and having a different build process for FreeBSD (and other unsupported platforms) is twice the workload for the people maintaining the build. I think what may be acceptable is not stop the move to BinaryBuilder for all supported platforms now, and have other platforms catch up later.
We already have working builds for all of these things, it's not like we have to develop them. If one of them stops working at some point then someone can choose to either fix it or just do the work to switch fully to using a builder. If we wait until we have all of the builds for all of the things to use any of them then we will never switch and we will never work out the bugs.
Sure. That makes sense.
@staticfloat Are you ok to move OpenBLASBuilder
to JuliaLinearAlgebra
. Perhaps OpenLibmBuilder
to JuliaMath
?
I need access to JuliaMath
to move OpenlibmBuilder
I've added you.
Getting close to having full BinaryBuilder coverage on Base libraries (even though Arpack and SuiteSparse need to move out, we have them ready now). The produced binaries need to be tested and such.
Should we move LLVMBuilder
to JuliaLang? Where should PcreBuilder
and all the curl, libgit2, unwind, mbedtls etc. go?
Is there an existing PR on how to enable Base to start using libraries from BinaryBuilder? Is LLVM the right one to look at? It will be great to use the same binaries for all developers, for releases, and reduce compile time overall.
I assume the process should be to basically just download the relevant tarball and untar it. Is there anything more to it than that?
Builders for curl, libgit2, and MbedTLS seem like they would be at home in the JuliaWeb organization.
@quinnj Would you be ok moving MBedTLSBuilder to JuliaWeb? I am happy to put the rest of these into BinaryBuilder form. Can someone give me owner access to JuliaWeb?
I guess libuv and libunwind should be in JuliaLang. What about utf8proc? JuliaStrings?
Since utf8proc lives in JuliaLang, a builder for it living here would make sense to me.
I'll add you to JuliaWeb. Edit: Never mind, I can't. (Member, not owner.)
We can move utf8proc to the JuliaStrings org. We could ask @nolta if he'd mind transferring ICU.jl to JuliaStrings and if @nalimilan is willing we could move StringEncodings.jl there too.
Also: dang, some progress has been made on this list.
MbedTLSBuilder is already in JuliaWeb............https://github.com/JuliaWeb/MbedTLSBuilder
Ah - it was just in the list above that we had the old URL. Updated it.
Perhaps LLVMBuilder should also go to JuliaLang?
We can move utf8proc to the JuliaStrings org. We could ask @nolta if he'd mind transferring ICU.jl to JuliaStrings and if @nalimilan is willing we could move StringEncodings.jl there too.
Fine with me for StringEncodings.jl. But there are currently two different repos for ICU.jl, and the one in JuliaString org includes a few significant fixes/improvements.
EDIT: I've just transferred StringEncodings.
I transferred utf8proc
as well.
Closing this with #31441
Most helpful comment
MbedTLSBuilder is already in JuliaWeb............https://github.com/JuliaWeb/MbedTLSBuilder