API reference
Types
BinaryBuilderBase.AbstractDependency
— TypeAn AbstractDependency
is a binary dependency of the JLL package. Dependencies are installed to ${prefix}
in the build environment.
Concrete subtypes of AbstractDependency
are
Dependency
: a JLL package that is necessary for to build the package and to load the generated JLL package.RuntimeDependency
: a JLL package that is necessary only at runtime. Its artifact will not be installed in the prefix during the build.BuildDependency
: a JLL package that is necessary only to build the package. This will not be a dependency of the generated JLL package.HostBuildDependency
: similar toBuildDependency
, but it will install the artifact for the host platform, instead of that for the target platform.
Subtypes of AbstractDependency
should define the following traits:
is_host_dependency
is_target_dependency
is_build_dependency
is_runtime_dependency
- [
is_top_level_dependency
][@ref]
BinaryBuilderBase.AbstractSource
— TypeAn AbstractSource
is something used as source to build the package. Sources are installed to ${WORKSPACE}/srcdir
in the build environment.
Concrete subtypes of AbstractSource
are:
ArchiveSource
: a remote archive to download from the Internet;FileSource
: a remote file to download from the Internet;GitSource
: a remote Git repository to clone;DirectorySource
: a local directory to mount.
BinaryBuilderBase.AnyPlatform
— TypeAnyPlatform()
A special platform to be used to build platform-independent tarballs, like those containing only header files. FileProduct
is the only product type allowed with this platform.
BinaryBuilderBase.ArchiveSource
— TypeArchiveSource(url::String, hash::String; unpack_target::String = "")
Specify a remote archive in one of the supported archive formats (e.g., TAR or ZIP balls) to be downloaded from the Internet from url
. hash
is the 64-character SHA256 checksum of the file.
In the builder environment, the archive will be automatically unpacked to ${WORKSPACE}/srcdir
, or in its subdirectory pointed to by the optional keyword unpack_target
, if provided.
BinaryBuilderBase.BuildDependency
— TypeBuildDependency(dep::Union{PackageSpec,String}; platforms)
Define a binary dependency that is necessary only to build the package. The dep
argument can be either a string with the name of the JLL package or a Pkg.PackageSpec
.
The optional keyword argument platforms
is a vector of AbstractPlatform
s which indicates for which platforms the dependency should be used. By default platforms=[AnyPlatform()]
, to mean that the dependency is compatible with all platforms.
BinaryBuilderBase.Dependency
— TypeDependency(dep::Union{PackageSpec,String}, build_version::VersionNumber;
compat::String, platforms::Vector{<:AbstractPlatform})
Define a binary dependency that is necessary to build the package and load the generated JLL package. The argument can be either a string with the name of the JLL package or a Pkg.PackageSpec
.
The optional positional argument build_version
can be used to specify the version of the dependency to be installed when building it. If not specified, the latest version of the package compatible with the environment will be automatically chosen by the package resolver, unless compat
is specified, see below.
The optional keyword argument compat
can be used to specify a string for use in the Project.toml
of the generated Julia package. If compat
is non-empty and build_version
is not passed, the latter defaults to the minimum version compatible with the compat
specifier.
The optional keyword argument platforms
is a vector of AbstractPlatform
s which indicates for which platforms the dependency should be used. By default platforms=[AnyPlatform()]
, to mean that the dependency is compatible with all platforms.
The optional keyword argument top_level
denotates that this dependency is platform independent. It implies that the platforms
keyword argument is set to [AnyPlatform()]
. The primary use-case is for packages that hold information about the platform selection using Preferences
. Platform selection is cached and in the case that no platform is available we need to be able to invalidate said cache. Invalidation occurs through the package that owns the Preferences
data.
BinaryBuilderBase.DirectorySource
— TypeDirectorySource(path::String; target::String = basename(path), follow_symlinks=false)
Specify a local directory to mount from path
.
The content of the directory will be mounted in ${WORKSPACE}/srcdir
, or in its subdirectory pointed to by the optional keyword target
, if provided. Symbolic links are replaced by a copy of the target when follow_symlinks
is true
.
BinaryBuilderBase.DockerRunner
— TypeDockerRunner
Use docker
as an execution engine; a reasonable backup for platforms that do not have user namespaces (e.g. MacOS, Windows).
BinaryBuilderBase.ExecutableProduct
— TypeAn ExecutableProduct
is a Product
that represents an executable file.
On all platforms, an ExecutableProduct checks for existence of the file. On non-Windows platforms, it will check for the executable bit being set. On Windows platforms, it will check that the file ends with ".exe", (adding it on automatically, if it is not already present).
ExecutableProduct(binname, varname::Symbol, dir_path="bin")
Declares an ExecutableProduct
that points to an executable located within the prefix. binname
specifies the basename of the executable, varname
is the name of the variable in the JLL package that can be used to call into the library. By default, the library is searched in the bindir
, but you can specify a different directory within the prefix with the dir_path
argument.
BinaryBuilderBase.FileProduct
— TypeFileProduct(path, varname::Symbol, dir_path = nothing)
Declares a FileProduct
that points to a file located relative to the root of a Prefix
, must simply exist to be satisfied. The first argument path
is either a single AbstractString
or a Vector{String}
to allow several paths to be checked.
BinaryBuilderBase.FileSource
— TypeFileSource(url::String, hash::String; filename::String = basename(url))
Specify a remote file to be downloaded from the Internet from url
. hash
is the 64-character SHA256 checksum of the file.
In the builder environment, the file will be saved under ${WORKSPACE}/srcdir
with the same name as the basename of the originating URL, unless the the keyword argument filename
is specified.
BinaryBuilderBase.FrameworkProduct
— TypeA FrameworkProduct
is a Product
that encapsulates a macOS Framework. It behaves mostly as a LibraryProduct
for now, but is a distinct type. This implies that for cross-platform builds where a library is provided as a Framework on macOS and as a normal library on other platforms, two calls to BinaryBuilder's build_tarballs
are needed: one with the LibraryProduct
and all non-macOS platforms, and one with the FrameworkProduct
and the MacOS
platforms.
FrameworkProduct(fwnames, varname::Symbol)
Declares a macOS FrameworkProduct
that points to a framework located within the prefix, with a name containing fwname
appended with .framework
. As an example, given that fwname
is equal to QtCore
, this would be satisfied by the following path:
lib/QtCore.framework
BinaryBuilderBase.GitSource
— TypeGitSource(url::String, hash::String; unpack_target::String = "")
Specify a remote Git repository to clone form url
. hash
is the 40-character SHA1 revision to checkout after cloning.
The repository will be cloned in ${WORKSPACE}/srcdir
, or in its subdirectory pointed to by the optional keyword unpack_target
, if provided.
BinaryBuilderBase.HostBuildDependency
— TypeHostBuildDependency(dep::Union{PackageSpec,String}; platforms)
Define a binary dependency that is necessary only to build the package. Different from the BuildDependency
, the artifact for the host platform will be installed, instead of that for the target platform.
The dep
argument can be either a string with the name of the JLL package or a Pkg.PackageSpec
.
The optional keyword argument platforms
is a vector of AbstractPlatform
s which indicates for which platforms the dependency should be used. By default platforms=[AnyPlatform()]
, to mean that the dependency is compatible with all platforms.
BinaryBuilderBase.LibraryProduct
— TypeA LibraryProduct
is a special kind of Product
that not only needs to exist, but needs to be dlopen()
'able. You must know which directory the library will be installed to, and its name, e.g. to build a LibraryProduct
that refers to "/lib/libnettle.so"
, the "directory" would be "/lib", and the "libname" would be "libnettle". Note that a LibraryProduct
can support multiple libnames, as some software projects change the libname based on the build configuration.
LibraryProduct(libname, varname::Symbol, dir_paths=String[];
dont_dlopen=false, dlopen_flags=Symbol[])
Declares a LibraryProduct
that points to a library located within the prefix. libname
specifies the basename of the library, varname
is the name of the variable in the JLL package that can be used to call into the library. By default, the library is searched in the libdir
, but you can add other directories within the prefix to the dir_paths
argument. You can specify the flags to pass to dlopen
as a vector of Symbols
with the dlopen_flags
keyword argument. If the library should not be dlopen'ed automatically by the JLL package, set dont_dlopen=true
.
For example, if the libname
is libnettle
, this would be satisfied by the following paths:
lib/libnettle.so
orlib/libnettle.so.6
on Linux and FreeBSD;lib/libnettle.6.dylib
on macOS;lib/libnettle-6.dll
on Windows.
Libraries matching the search pattern are rejected if they are not dlopen()
'able.
If you are unsure what value to use for libname
, you can use Base.BinaryPlatforms.parse_dl_name_version
:
julia> using Base.BinaryPlatforms
julia> parse_dl_name_version("sfml-audio-2.dll", "windows")[1]
"sfml-audio"
If the library would have different basenames on different operating systems (e.g., libz.so
on Linux and FreeBSD, libz.dylib
on macOS, and zlib.dll
on Windows), libname
can be also a vector of String
s with the different alternatives:
LibraryProduct(["libz", "zlib"], :libz)
BinaryBuilderBase.Product
— TypeA Product
is an expected result after building or installation of a package.
Examples of Product
s include LibraryProduct
, FrameworkProduct
, ExecutableProduct
and FileProduct
. All Product
types must define the following minimum set of functionality:
locate(::Product)
: given aProduct
, locate it within the wrappedPrefix
returning its location as a stringsatisfied(::Product)
: given aProduct
, determine whether it has been successfully satisfied (e.g. it is locateable and it passes all callbacks)variable_name(::Product)
: return the variable name assigned to aProduct
repr(::Product)
: Return a representation of thisProduct
, useful for auto-generating source code that constructsProducts
, if that's your thing.
BinaryBuilderBase.RuntimeDependency
— TypeRuntimeDependency(dep::Union{PackageSpec,String}; compat::String, platforms::Vector{<:AbstractPlatform}, top_level::Bool=false)
Define a binary dependency that is only listed as dependency of the generated JLL package, but its artifact is not installed in the prefix during the build. The dep
argument can be either a string with the name of the JLL package or a Pkg.PackageSpec
.
The optional keyword argument compat
can be used to specify a string for use in the Project.toml
of the generated Julia package.
The optional keyword argument platforms
is a vector of AbstractPlatform
s which indicates for which platforms the dependency should be used. By default platforms=[AnyPlatform()]
, to mean that the dependency is compatible with all platforms.
The optional keyword argument top_level
specifies whether the dependency should be use only at the top-level of the generated JLL package, instead of inside each platform-specific wrapper. Using top_level=true
is useful for packages needed for platform augmentation (e.g. MPIPreferences.jl
).
BinaryBuilderBase.UserNSRunner
— TypeUserNSRunner
A UserNSRunner
represents an "execution context", an object that bundles all necessary information to run commands within the container that contains our crossbuild environment. Use run()
to actually run commands within the UserNSRunner
, and runshell()
as a quick way to get an interactive shell within the crossbuild environment.
BinaryBuilder.Wizard.WizardState
— TypeWizardState
Building large dependencies can take a lot of time. This state object captures all relevant state of this function. It can be passed back to the function to resume where we left off. This can aid debugging when code changes are necessary. It also holds all necessary metadata such as input/output streams.
Functions
BinaryBuilderBase.abi_agnostic
— Methodabi_agnostic(p::AbstractPlatform)
Strip out any tags that are not the basic annotations like libc
and call_abi
.
BinaryBuilderBase.accept_apple_sdk
— Methodaccept_apple_sdk(ins::IO, outs::IO) -> Bool
Ask the user whether they accept the terms of the macOS SDK, and return a boolean with their choice. Write messages to outs
, read input from ins
.
BinaryBuilderBase.artifact_name
— Methodartifact_name(cs::CompilerShard)
Return the bound artifact name for a particular shard.
BinaryBuilderBase.bindir
— Methodbindir(prefix::Prefix)
Returns the binary directory for the given prefix
.
BinaryBuilderBase.choose_shards
— Methodchoose_shards(p::AbstractPlatform; rootfs_build, ps_build, GCC_builds,
LLVM_builds, archive_type)
This method chooses, given a Platform
, which shards to download, extract and mount, returning a list of CompilerShard
objects. At the moment, this always consists of four shards, but that may not always be the case.
BinaryBuilderBase.chown_cleanup
— Methodchown_cleanup(dr::DockerRunner)
On Linux, the user id inside of the docker container doesn't correspond to ours on the outside, so permissions get all kinds of screwed up. To fix this, we have to chown -R $(id -u):$(id -g) $prefix
, which really sucks, but is still better than nothing. This is why we prefer the UserNSRunner on Linux.
BinaryBuilderBase.collect_jll_uuids
— Methodcollect_jll_uuids(manifest::Pkg.Types.Manifest, dependencies::Set{Base.UUID})
Return a Set
of all JLL packages in the manifest
with dependencies
being the list of direct dependencies of the environment.
BinaryBuilderBase.compress_dir
— Methodcompress_dir(dir::AbstractString;
compressor_stream = GzipCompressorStream,
level::Int = 9,
extension::AbstractString = ".gz",
verbose::Bool = false)
Compress all files in dir
using the specified compressor_stream
with compression level equal to level
, appending extension
to the filenames. Remove the original uncompressed files at the end.
BinaryBuilderBase.download_all_artifacts
— Methoddownload_all_artifacts(; verbose::Bool=false)
Helper function to download all shards/helper binaries so that no matter what happens, you don't need an internet connection to build your precious, precious binaries.
BinaryBuilderBase.download_source
— Functiondownload_source(source::AbstractSource; verbose::Bool = false)
Download the given source
. All downloads are cached within the BinaryBuilder downloads
storage directory.
BinaryBuilderBase.enable_apple_file
— Methodenable_apple_file()
Return the path to file that, if exists, indicates that the user accepts to download macOS SDK. The file is automatically created when the package is loaded if the environment variable BINARYBUILDER_AUTOMATIC_APPLE
is set to "true"
.
BinaryBuilderBase.expand_cxxstring_abis
— Methodexpand_cxxstring_abis(p::AbstractPlatform; skip=Sys.isbsd)
Given a Platform
, returns an array of Platforms
with a spread of identical entries with the exception of the cxxstring_abi
tag within the Platform
object. This is used to take, for example, a list of supported platforms and expand them to include multiple GCC versions for the purposes of ABI matching.
If the given Platform
already specifies a cxxstring_abi
(as opposed to nothing
) only that Platform
is returned. If skip
is a function for which skip(platform)
evaluates to true
, the given platform is not expanded. By default FreeBSD and macOS platforms are skipped, due to their lack of a dependence on libstdc++
and not needing this compatibility shim.
BinaryBuilderBase.expand_gfortran_versions
— Methodexpand_gfortran_versions(p::AbstractPlatform)
Given a Platform
, returns an array of Platforms
with a spread of identical entries with the exception of the libgfortran_version
tag within the Platform
. This is used to take, for example, a list of supported platforms and expand them to include multiple GCC versions for the purposes of ABI matching. If the given Platform
already specifies a libgfortran_version
(as opposed to nothing
) only that Platform
is returned.
BinaryBuilderBase.expand_microarchitectures
— Functionexpand_microarchitectures(p::AbstractPlatform, [microarchitectures::Vector{String}])
Given a Platform
, returns a vector of Platforms
with differing march
attributes as specified by the ARCHITECTURE_FLAGS
mapping. If the given Platform
alread has a march
tag specified, only that platform is returned. If the microarchitectures
argument is given, limit the expansion to the given microarchitectures.
julia> using BinaryBuilderBase
julia> expand_microarchitectures(Platform("x86_64", "freebsd"))
4-element Vector{Platform}:
FreeBSD x86_64 {march=x86_64}
FreeBSD x86_64 {march=avx}
FreeBSD x86_64 {march=avx2}
FreeBSD x86_64 {march=avx512}
julia> expand_microarchitectures(Platform("armv7l", "linux"))
2-element Vector{Platform}:
Linux armv7l {call_abi=eabihf, libc=glibc, march=armv7l}
Linux armv7l {call_abi=eabihf, libc=glibc, march=neonvfpv4}
julia> expand_microarchitectures(Platform("aarch64", "linux"), ["armv8_0", "a64fx"])
2-element Vector{Platform}:
Linux aarch64 {libc=glibc, march=armv8_0}
Linux aarch64 {libc=glibc, march=a64fx}
julia> expand_microarchitectures(Platform("i686", "windows"))
2-element Vector{Platform}:
Windows i686 {march=pentium4}
Windows i686 {march=prescott}
BinaryBuilderBase.expand_microarchitectures
— Functionexpand_microarchitectures(ps::Vector{<:Platform}, [microarchitectures::Vector{String}];
filter=Returns(true))
Expand all platforms in the vector ps
with the supported microarchitectures.
If the microarchitectures
argument is given, limit the expansion to the given platforms. This is useful if you do not want to expand to all available microarchitectures.
The expansion is applied only to the platforms matching the filter
predicate, by default all platforms. This is useful if you want to limit the expansion to some platforms, without having to explicitly list its microarchitectures in the second argument.
julia> using BinaryBuilderBase
julia> expand_microarchitectures(filter!(p -> Sys.islinux(p) && libc(p) == "glibc", supported_platforms()))
14-element Vector{Platform}:
Linux i686 {libc=glibc, march=pentium4}
Linux i686 {libc=glibc, march=prescott}
Linux x86_64 {libc=glibc, march=x86_64}
Linux x86_64 {libc=glibc, march=avx}
Linux x86_64 {libc=glibc, march=avx2}
Linux x86_64 {libc=glibc, march=avx512}
Linux aarch64 {libc=glibc, march=armv8_0}
Linux aarch64 {libc=glibc, march=armv8_1}
Linux aarch64 {libc=glibc, march=armv8_2_crypto}
Linux aarch64 {libc=glibc, march=a64fx}
Linux armv6l {call_abi=eabihf, libc=glibc, march=arm1176jzfs}
Linux armv7l {call_abi=eabihf, libc=glibc, march=armv7l}
Linux armv7l {call_abi=eabihf, libc=glibc, march=neonvfpv4}
Linux powerpc64le {libc=glibc, march=power8}
julia> expand_microarchitectures(filter!(p -> Sys.islinux(p) && libc(p) == "glibc", supported_platforms()), ["x86_64", "avx2"])
7-element Vector{Platform}:
Linux i686 {libc=glibc}
Linux x86_64 {libc=glibc, march=x86_64}
Linux x86_64 {libc=glibc, march=avx2}
Linux aarch64 {libc=glibc}
Linux armv6l {call_abi=eabihf, libc=glibc}
Linux armv7l {call_abi=eabihf, libc=glibc}
Linux powerpc64le {libc=glibc}
julia> expand_microarchitectures(filter!(p -> Sys.islinux(p) && libc(p) == "glibc", supported_platforms()); filter=p->arch(p)=="x86_64")
9-element Vector{Platform}:
Linux i686 {libc=glibc}
Linux x86_64 {libc=glibc, march=x86_64}
Linux x86_64 {libc=glibc, march=avx}
Linux x86_64 {libc=glibc, march=avx2}
Linux x86_64 {libc=glibc, march=avx512}
Linux aarch64 {libc=glibc}
Linux armv6l {call_abi=eabihf, libc=glibc}
Linux armv7l {call_abi=eabihf, libc=glibc}
Linux powerpc64le {libc=glibc}
BinaryBuilderBase.filter_platforms
— Methodfilter_platforms(deps::AbstractVector{<:AbstractDependency}, p::AbstractPlatform)
Filter the dependencies deps
which are compatible with platform p
.
BinaryBuilderBase.gcc_version
— Functiongcc_version(p::AbstractPlatform, GCC_builds::Vector{GCCBuild},
compilers::Vector{Symbol}=[:c];
llvm_version::Union{Nothing,VersionNumber}=nothing)
Returns the closest matching GCC version number for the given particular platform, from the given set of options. The compiler ABI and the microarchitecture of the platform will be taken into account. If no match is found, returns an empty list. compilers
is the list of compilers used in the build, to choose the right version of GCC to couple with them if necessary. If the keyword argument llvm_version
is passed, it is used to filter the version of GCC for FreeBSD platforms.
This method assumes that the compiler ABI of the platform represents a platform that binaries will be run on, and thus versions are always rounded down; e.g. if the platform supports a libstdc++
version that corresponds to GCC 5.1.0
, but the only GCC versions available to be picked from are 4.8.5
and 5.2.0
, it will return 4.8.5
, as binaries compiled with that version will run on this platform, whereas binaries compiled with 5.2.0
may not.
BinaryBuilderBase.generate_compiler_wrappers!
— Methodgenerate_compiler_wrappers!(platform::AbstractPlatform; bin_path::AbstractString,
host_platform::AbstractPlatform = Platform("x86_64", "linux"; libc = "musl", cxxstring_abi = "cxx11"),
compilers::Vector{Symbol} = [:c],
allow_unsafe_flags::Bool = false,
lock_microarchitecture::Bool = true,
gcc_version::Union{Nothing,VersionNumber}=nothing,
clang_version::Union{Nothing,VersionNumber}=nothing,
clang_use_lld::Bool = false,
)
We generate a set of compiler wrapper scripts within our build environment to force all build systems to honor the necessary sets of compiler flags to build for our systems. Note that while platform_envs()
sets many environment variables, those values are intended to be optional/overridable. These values, while still overridable by directly invoking a compiler binary directly (e.g. /opt/{target}/bin/{target}-gcc), are much more difficult to override, as the flags embedded in these wrappers are absolutely necessary, and even simple programs will not compile without them.
BinaryBuilderBase.generate_per_uid_squashfs
— Functiongenerate_per_uid_squashfs(cs, new_uid = getuid())
In order for the sandbox to work well, we need to have the uids of the squashfs images match the uid of the current unprivileged user. Unfortunately there is no mount-time option to do this for us. Fortunately, squashfs is simple enough that if the ID table is uncompressed, we can just manually patch the uids to be what we need. This function performs this operation, by rewriting all UIDs and GIDs to the given new_uid
(which defaults to the current user's UID).
BinaryBuilderBase.get_addable_spec
— Methodget_addable_spec(name::AbstractString, version::VersionNumber)
Given a JLL name and registered version, return a PackageSpec
that, when passed as a Dependency
, ensures that exactly that version will be installed. Example usage:
dependencies = [
BuildDependency(get_addable_spec("LLVM_jll", v"9.0.1+0")),
]
BinaryBuilderBase.get_commit_sha
— Methodget_commit_sha(url::String, tree_hash::Base.SHA1; verbose::Bool=false)
Find the latest git commit corresponding to the given git tree SHA1 for the remote repository with the given url
. The repository is cached locally for quicker future access. If verbose
is true
, print to screen some debugging information.
The return value is the commit SHA as a String
, if the corresponding revision is found, nothing
otherwise.
BinaryBuilderBase.get_concrete_platform
— Methodget_concrete_platform(platform::AbstractPlatform;
preferred_gcc_version = nothing,
preferred_llvm_version = nothing,
compilers = nothing)
Return the concrete platform for the given platform
based on the GCC compiler ABI. The set of shards is chosen by the keyword arguments (see choose_shards
).
BinaryBuilderBase.get_concrete_platform
— Methodget_concrete_platform(platform::Platform, shards::Vector{CompilerShard})
Return the concrete platform for the given platform
based on the GCC compiler ABI in the shards
.
BinaryBuilderBase.get_tree_hash
— Methodget_tree_hash(tree::LibGit2.GitTree)
Given a GitTree
, get the GitHash
that identifies it.
BinaryBuilderBase.getgid
— Methodgetgid()
Wrapper around libc's getgid()
function
BinaryBuilderBase.getuid
— Methodgetuid()
Wrapper around libc's getuid()
function
BinaryBuilderBase.import_docker_image
— Methodimport_docker_image(rootfs::CompilerShard; verbose::Bool = false)
Checks to see if the given rootfs has been imported into docker yet; if it hasn't, then do so so that we can run things like:
docker run -ti binarybuilder_rootfs:v2018.08.27 /bin/bash
Which, after all, is the foundation upon which this whole doodad is built.
BinaryBuilderBase.includedir
— Methodincludedir(prefix::Prefix)
Returns the include directory for the given prefix
BinaryBuilderBase.installed_shards
— Methodinstalled_shards()
Return a vector of compiler shards currently downloaded on the local system
BinaryBuilderBase.is_build_dependency
— Functionis_build_dependency(dep::AbstractDependency) -> Bool
Return whether dep
is a build-time dependency or not.
BinaryBuilderBase.is_ecryptfs
— Methodis_ecryptfs(path::AbstractString; verbose::Bool=false)
Checks to see if the given path
(or any parent directory) is placed upon an ecryptfs
mount. This is known not to work on current kernels, see this bug for more details: https://bugzilla.kernel.org/show_bug.cgi?id=197603
This method returns whether it is encrypted or not, and what mountpoint it used to make that decision.
BinaryBuilderBase.is_host_dependency
— Functionis_host_dependency(dep::AbstractDependency) -> Bool
Return whether dep
is a dependency of the host platform or not.
BinaryBuilderBase.is_mounted
— Methodis_mounted(cs::CompilerShard, build_prefix::String)
Return true if the given shard is mounted. Uses run()
so will error out if something goes awry.
BinaryBuilderBase.is_runtime_dependency
— Functionis_runtime_dependency(dep::AbstractDependency) -> Bool
Return whether dep
is a runtime dependency or not.
BinaryBuilderBase.is_target_dependency
— Methodis_target_dependency(dep::AbstractDependency) -> Bool
Return whether dep
is a dependency of the target platform or not.
BinaryBuilderBase.is_top_level_dependency
— Methodis_top_level_dependency(dep::AbstractDependency) -> Bool
Return wheter dep
is a top-level dependency or not.
BinaryBuilderBase.libabi_agnostic
— Methodabi_agnostic(p::AbstractPlatform)
Like abi_agnostic
, but keep the sanitizer ABI tags.
BinaryBuilderBase.libdirs
— Functionlibdirs(prefix::Prefix, platform = HostPlatform())
Returns the library directories for the given prefix
(note that this differs between unix systems and windows systems, and between 32- and 64-bit systems).
BinaryBuilderBase.locate
— Methodlocate(ep::ExecutableProduct, prefix::Prefix;
platform::AbstractPlatform = HostPlatform(),
verbose::Bool = false,
isolate::Bool = false)
If the given executable file exists and is executable, return its path.
On all platforms, an ExecutableProduct
checks for existence of the file. On non-Windows platforms, it will check for the executable bit being set. On Windows platforms, it will check that the file ends with ".exe", (adding it on automatically, if it is not already present).
BinaryBuilderBase.locate
— Methodlocate(fp::FileProduct, prefix::Prefix;
platform::AbstractPlatform = HostPlatform(),
verbose::Bool = false,
isolate::Bool = false)
If the given file exists, return its path. The platform
and isolate
arguments are is ignored here, but included for uniformity. For ease of use, we support a limited number of custom variable expansions such as ${target}
, and ${nbits}
, so that the detection of files within target-specific folders named things like /lib32/i686-linux-musl
is simpler.
BinaryBuilderBase.locate
— Methodlocate(lp::LibraryProduct, prefix::Prefix;
verbose::Bool = false,
platform::AbstractPlatform = HostPlatform())
If the given library exists (under any reasonable name) and is dlopen()
able, (assuming it was built for the current platform) return its location. Note that the dlopen()
test is only run if the current platform matches the given platform
keyword argument, as cross-compiled libraries cannot be dlopen()
ed on foreign platforms.
BinaryBuilderBase.logdir
— Methodlogdir(prefix::Prefix; subdir::AbstractString="")
Returns the logs directory for the given prefix
. If subdir
is a non-empty string, that directory it is appended to the logdir of the given prefix
.
BinaryBuilderBase.macos_sdk_already_installed
— Methodmacos_sdk_already_installed()
Returns true
if any piece of the MacOS SDK is already installed.
BinaryBuilderBase.manage_shards
— Methodmanage_shards(; sort_by=:name, rev=false)
Open a prompt allowing a user to selectively remove downloaded compiler shards. By default, the shards are sorted by name, alternatively you can sort them by file size on disk by specifying sort_by=:size
. With rev=true
you can reverse the sort order.
BinaryBuilderBase.map_target
— Methodmap_target(cs::CompilerShard)
Return the location this compiler shard should be mounted at. We basically analyze the name and platform of this shard and return a path based on that.
BinaryBuilderBase.mount
— Methodmount(cs::CompilerShard, build_prefix::String)
Mount a compiler shard, if possible. Uses run()
so will error out if something goes awry. Note that this function only does something when using a .squashfs
shard, with a UserNS or Docker runner, on Linux. All other combinations of shard archive type, runner and platform result in a no-op from this function.
BinaryBuilderBase.package
— Methodpackage(prefix::Prefix, output_base::AbstractString,
version::VersionNumber;
platform::AbstractPlatform = HostPlatform(),
verbose::Bool = false, force::Bool = false,
filter = Returns(true))
Build a tarball of the prefix
, storing the tarball at output_base
, appending the version number version
, a platform-dependent suffix and a file extension. If platform
is not given, defaults to current platform. Returns the full path to, the SHA256 hash and the git tree SHA1 of the generated tarball.
The are additional keyword arguments:
verbose
controls whether to print information to screen,force
makes the function overwrite an existing tarball with the same namefilter
is a 2-argument function which returnstrue
if the given file or directory should be packaged, andfalse
otherwise. The arguments are(prefix, path)
, whereprefix
is the directory where the prefix is stored, andpath
is the path, within the prefix, of the file or directory. This keyword allows you to filter out from the tarball certain files or directories.
BinaryBuilderBase.platform_envs
— Methodplatform_envs(platform::AbstractPlatform, src_name::AbstractString;
host_platform = default_host_platform,
bootstrap::Bool=!isempty(bootstrap_list),
compilers::Vector{Symbol}=[:c],
rust_version::Union{Nothing,VersionNumber}=nothing,
verbose::Bool = false,
)
Given a platform
and a src_name
, generate a Dict
mapping representing all the environment variables to be set within the build environment to force compiles toward the defined target architecture. Examples of things set are PATH
, CC
, RANLIB
, as well as nonstandard things like target
.
Accepted keyword arguments are:
host_platform
: the platform of the host system,bootstraop
: iftrue
, only basic environment variables will be generated,compilers
: list of compilers, some environment variables will be generated only if the relevant compilers are used (e.g., for Go and Rust),rust_version
: version of the Rust toolchain, needed to set the environment variableRUSTUP_TOOLCHAIN
,verbose
: holds the value of theV
andVERBOSE
environment variables.
BinaryBuilderBase.platform_exeext
— Methodplatform_exeext(p::AbstractPlatform)
Get the executable extension for the given Platform. Includes the leading .
.
BinaryBuilderBase.preferred_cxxstring_abi
— Methodpreferred_cxxstring_abi(platform::AbstractPlatform, shard::CompilerShard;
gcc_builds::Vector{GCCBuild} = available_gcc_builds)
Return the C++ string ABI preferred by the given platform or GCCBootstrap shard.
BinaryBuilderBase.preferred_libgfortran_version
— Methodpreferred_libgfortran_version(platform::AbstractPlatform, shard::CompilerShard;
gcc_builds::Vector{GCCBuild} = available_gcc_builds)
Return the libgfortran version preferred by the given platform or GCCBootstrap shard.
BinaryBuilderBase.runshell
— Functionrunshell(platform::AbstractPlatform = HostPlatform())
Launch an interactive shell session within the user namespace, with environment setup to target the given platform
.
BinaryBuilderBase.satisfied
— Methodsatisfied(p::Product;
platform::AbstractPlatform = HostPlatform(),
verbose::Bool = false,
isolate::Bool = false)
Given a Product
, return true
if that Product
is satisfied, e.g. whether a file exists that matches all criteria setup for that Product
. If isolate
is set to true
, will isolate all checks from the main Julia process in the event that dlopen()
'ing a library might cause issues.
BinaryBuilderBase.setup_workspace
— Functionsetup_workspace(build_path::String, sources::Vector{SetupSource};
verbose::Bool = false)
Sets up a workspace within build_path
, creating the directory structure needed by further steps, unpacking the source within build_path
, and defining the environment variables that will be defined within the sandbox environment.
This method returns the Prefix
to install things into, and the runner that can be used to launch commands within this workspace.
BinaryBuilderBase.shard_mappings
— Methodshard_mappings(shards::Vector{CompilerShard})
Return the default mappings for a set of compiler shards
BinaryBuilderBase.shard_path
— Methodshard_path(cs::CompilerShard)
Return the path to this shard on-disk; for unpacked shards, this is a directory. For squashfs shards, this is a file. This will not cause a shard to be downloaded.
BinaryBuilderBase.supported_platforms
— Methodsupported_platforms(;exclude::Union{Vector{<:Platform},Function}=Returns(false),
experimental::Bool=false)
Return the list of supported platforms as an array of Platform
s. These are the platforms we officially support building for, if you see a mapping in get_shard_hash()
that isn't represented here, it's probably because that platform is still considered "in beta". If experimental=true
, include platforms considered experimental.
Platforms can be excluded from the list by specifying an array of platforms to exclude
i.e. supported_platforms(exclude=[Platform("i686", "windows"), Platform("x86_64", "windows")])
or a function that returns true for exclusions i.e.
supported_platforms(exclude=Sys.islinux)
BinaryBuilderBase.temp_prefix
— Methodtemp_prefix(func::Function)
Create a temporary prefix, passing the prefix into the user-defined function so that build/packaging operations can occur within the temporary prefix, which is then cleaned up after all operations are finished. If the path provided exists already, it will be deleted.
Usage example:
out_path = abspath("./libfoo")
temp_prefix() do p
# <insert build steps here>
# tarball up the built package
tarball_path, tarball_hash = package(p, out_path)
end
BinaryBuilderBase.uname
— Methoduname()
On Linux systems, return the strings returned by the uname()
function in libc
BinaryBuilderBase.unmount
— Methodunmount(cs::CompilerShard, build_prefix::String)
Unmount a compiler shard from a given build prefix, if possible. Uses run()
so will error out if something goes awry. Note that this function only does something when using a squashfs shard on Linux. All other combinations of shard archive type and platform result in a no-op.
BinaryBuilderBase.variable_name
— Methodvariable_name(p::Product)
Return the variable name associated with this Product
as a string
BinaryBuilderBase.versioninfo
— Methodversioninfo()
Helper function to print out some debugging information
BinaryBuilder.autobuild
— Methodautobuild(dir::AbstractString, src_name::AbstractString,
src_version::VersionNumber, sources::Vector,
script::AbstractString, platforms::Vector,
products::Vector, dependencies::Vector;
verbose = false, debug = false,
skip_audit = false, ignore_audit_errors = true,
autofix = true, code_dir = nothing,
meta_json_file = nothing, require_license = true,
dont_dlopen = false, kwargs...)
Runs the boiler plate code to download, build, and package a source package for a list of platforms. This method takes a veritable truckload of arguments, here are the relevant actors, broken down in brief:
dir
: the root of the build; products will be placed withindir
/products, and mountpoints will be placed withindir
/build/.src_name
: the name of the source package being built and will set the name of the built tarballs.src_version
: the version of the source package.platforms
: a list of platforms to build for.sources
: a vector of all sources to download and unpack before building begins, asAbstractSource
s.script
: a string representing a shell script to run as the build.products
: the list ofProduct
s which shall be built.dependencies
: a vector of JLL dependency packages asAbstractDependency
that should be installed before building begins.verbose
: Enable verbose mode. What did you expect?debug
: cause a failed build to drop into an interactive shell so that the build can be inspected easily.skip_audit
: disable the typical audit that occurs at the end of a build.ignore_audit_errors
: do not kill a build even if a problem is found.autofix
: giveBinaryBuilder
permission to automatically fix issues it finds during audit passes. Highly recommended.code_dir
: sets where autogenerated JLL packages will be put.require_license
enables a special audit pass that requires licenses to be installed by all packages.dont_dlopen
: don't try todlopen
library products. This is separate from specifyingdont_dlopen
on aLibraryProduct
in that it still results in the generated JLL loading the library at run time, and only prevents BinaryBuilder from doing so during JLL generation.
BinaryBuilder.get_compilers_versions
— Methodget_compilers_versions(; compilers = [:c])
Return the script string that is used to print the versions of the given compilers
.
Base.BinaryPlatforms.detect_cxxstring_abi
— Methoddetect_cxxstring_abi(oh::ObjectHandle, platform::AbstractPlatform)
Given an ObjectFile, examine its symbols to discover which (if any) C++11 std::string ABI it's using. We do this by scanning the list of exported symbols, triggering off of instances of St7__cxx11
or _ZNSs
to give evidence toward a constraint on cxx11
, cxx03
or neither.
Base.BinaryPlatforms.detect_libstdcxx_version
— Methoddetect_libstdcxx_version(oh::ObjectHandle, platform::AbstractPlatform)
Given an ObjectFile, examine its dynamic linkage to discover which (if any) libgfortran
it's linked against. The major SOVERSION will determine which GCC version we're restricted to.
BinaryBuilder.Auditor.analyze_instruction_set
— Methodanalyze_instruction_set(oh::ObjectHandle, platform::AbstractPlatform; verbose::Bool = false)
Analyze the instructions within the binary located at the given path for which minimum instruction set it requires, taking note of groups of instruction sets used such as avx
, sse4.2
, i486
, etc....
Some binary files (such as libopenblas) contain multiple versions of functions, internally determining which version to call by using the cpuid
instruction to determine processor support. In an effort to detect this, we make note of any usage of the cpuid
instruction, disabling our minimum instruction set calculations if such an instruction is found, and notifying the user of this if verbose
is set to true
.
Note that this function only really makes sense for x86/x64 binaries. Don't run this on armv7l, aarch64, ppc64le etc... binaries and expect it to work.
BinaryBuilder.Auditor.audit
— Functionaudit(prefix::Prefix, src_name::AbstractString = "";
io=stderr,
platform::AbstractPlatform = HostPlatform(),
verbose::Bool = false,
silent::Bool = false,
autofix::Bool = false,
has_csl::Bool = true,
require_license::Bool = true,
)
Audits a prefix to attempt to find deployability issues with the binary objects that have been installed within. This auditing will check for relocatability issues such as dependencies on libraries outside of the current prefix
, usage of advanced instruction sets such as AVX2 that may not be usable on many platforms, linkage against newer glibc symbols, etc...
This method is still a work in progress, only some of the above list is actually implemented, be sure to actually inspect Auditor.jl
to see what is and is not currently in the realm of fantasy.
BinaryBuilder.Auditor.check_license
— Functioncheck_license(prefix, src_name; verbose::Bool = false,, silent::Bool = false)
Check that there are license files for the project called src_name
in the prefix
.
BinaryBuilder.Auditor.collapse_symlinks
— Methodcollapse_symlinks(files::Vector{String})
Given a list of files, prune those that are symlinks pointing to other files within the list.
BinaryBuilder.Auditor.collect_files
— Functioncollect_files(path::AbstractString, predicate::Function = f -> true)
Find all files that satisfy predicate()
when the full path to that file is passed in, returning the list of file paths.
BinaryBuilder.Auditor.compatible_marchs
— Methodcompatible_marchs(p::AbstractPlatform)
Return a (sorted) list of compatible microarchitectures, starting from the most compatible to the most highly specialized. If no microarchitecture is specified within p
, returns the most generic microarchitecture possible for the given architecture.
BinaryBuilder.Auditor.detect_libgfortran_version
— Methoddetect_libgfortran_version(oh::ObjectHandle, platform::AbstractPlatform)
Given an ObjectFile, examine its dynamic linkage to discover which (if any) libgfortran
it's linked against. The major SOVERSION will determine which GCC version we're restricted to.
BinaryBuilder.Auditor.instruction_mnemonics
— Methodinstruction_mnemonics(path::AbstractString, platform::AbstractPlatform)
Dump a binary object with objdump
, returning a list of instruction mnemonics for further analysis with analyze_instruction_set()
.
Note that this function only really makes sense for x86/x64 binaries. Don't run this on armv7l, aarch64, ppc64le etc... binaries and expect it to work.
This function returns the list of mnemonics as well as the counts of each, binned by the mapping defined within instruction_categories
.
BinaryBuilder.Auditor.is_for_platform
— Methodis_for_platform(h::ObjectHandle, platform::AbstractPlatform)
Returns true
if the given ObjectHandle
refers to an object of the given platform
; E.g. if the given platform
is for AArch64 Linux, then h
must be an ELFHandle
with h.header.e_machine
set to ELF.EM_AARCH64
.
In particular, this method and platform_for_object()
both exist because the latter is not smart enough to deal with :glibc
and :musl
yet.
BinaryBuilder.Auditor.is_troublesome_library_link
— Methodis_troublesome_library_link(libname::AbstractString, platform::AbstractPlatform)
Return true
if depending on libname
is known to cause problems at runtime, false
otherwise.
BinaryBuilder.Auditor.minimum_march
— Methodminimum_march(counts::Dict, p::AbstractPlatform)
This function returns the minimum instruction set required, depending on whether the object file being pointed to is a 32-bit or 64-bit one:
For 32-bit object files, this returns one of ["i686", "prescott"]
For 64-bit object files, this returns one of ["x86_64", "avx", "avx2", "avx512"]
BinaryBuilder.Auditor.platform_for_object
— Methodplatform_for_object(oh::ObjectHandle)
Returns the platform the given ObjectHandle
should run on. E.g. if the given ObjectHandle
is an x86_64
Linux ELF object, this function will return Platform("x86_64", "linux")
. This function does not yet distinguish between different libc's such as :glibc
and :musl
.
BinaryBuilder.Auditor.symlink_soname_lib
— Methodsymlink_soname_lib(path::AbstractString)
We require that all shared libraries are accessible on disk through their SONAME (if it exists). While this is almost always true in practice, it doesn't hurt to make doubly sure.
BinaryBuilder.Auditor.translate_symlinks
— Methodtranslate_symlinks(root::AbstractString; verbose::Bool=false)
Walks through the root directory given within root
, finding all symlinks that point to an absolute path within root
, and rewriting them to be a relative symlink instead, increasing relocatability.
BinaryBuilder.Auditor.update_linkage
— Methodupdate_linkage(prefix::Prefix, platform::AbstractPlatform, path::AbstractString,
old_libpath, new_libpath; verbose::Bool = false)
Given a binary object located at path
within prefix
, update its dynamic linkage to point to new_libpath
instead of old_libpath
. This is done using a tool within the cross-compilation environment such as install_name_tool
on MacOS or patchelf
on Linux. Windows platforms are completely skipped, as they do not encode paths or RPaths within their executables.
BinaryBuilder.Auditor.warn_deadlinks
— Methodwarn_deadlinks(root::AbstractString)
Walks through the given root
directory, finding broken symlinks and warning the user about them. This is used to catch instances such as a build recipe copying a symlink that points to a dependency; by doing so, it implicitly breaks relocatability.
BinaryBuilder.Wizard.canonicalize_file_url
— MethodCanonicalize URL to a file within a GitHub repo
BinaryBuilder.Wizard.canonicalize_source_url
— MethodCanonicalize a GitHub repository URL
BinaryBuilder.Wizard.change_script!
— MethodChange the script. This will invalidate all platforms to make sure we later
verify that they still build with the new script.
BinaryBuilder.Wizard.download_source
— Methoddownload_source(state::WizardState)
Ask the user where the source code is coming from, then download and record the relevant parameters, returning the source url
, the local path
it is stored at after download, and a hash
identifying the version of the code. In the case of a git
source URL, the hash
will be a git treeish identifying the exact commit used to build the code, in the case of a tarball, it is the sha256
hash of the tarball itself.
BinaryBuilder.Wizard.edit_script
— Methodedit_script(state::WizardState, script::AbstractString)
For consistency (and security), use the sandbox for editing a script, launching vi
within an interactive session to edit a buildscript.
BinaryBuilder.Wizard.filter_object_files
— Methodfilter_object_files(files)
Given a list of files, filter out any that cannot be opened by readmeta()
from ObjectFile
.
BinaryBuilder.Wizard.interactive_build
— Methodinteractive_build(state::WizardState, prefix::Prefix,
ur::Runner, build_path::AbstractString)
Runs the interactive shell for building, then captures bash history to save
reproducible steps for building this source. Shared between steps 3 and 5
BinaryBuilder.Wizard.match_files
— Methodmatch_files(state::WizardState, prefix::Prefix,
platform::AbstractPlatform, files::Vector; silent::Bool = false)
Inspects all binary files within a prefix, matching them with a given list of files
, complaining if there are any files that are not properly matched and returning the set of normalized names that were not matched, or an empty set if all names were properly matched.
BinaryBuilder.Wizard.normalize_name
— Methodnormalize_name(file::AbstractString)
Given a filename, normalize it, stripping out extensions. E.g. the file path "foo/libfoo.tar.gz"
would get mapped to "libfoo"
.
BinaryBuilder.Wizard.pick_preferred_platform
— MethodPick the first platform for use to run on. We prefer Linux x86_64 because that's generally the host platform, so it's usually easiest. After that we go by the following preferences:
- OS (in order): Linux, Windows, OSX
- Architecture: x86_64, i686, aarch64, powerpc64le, armv7l
- The first remaining after this selection
BinaryBuilder.Wizard.print_autoconf_hint
— Methodprint_autoconf_hint(state::WizardState)
Print a hint for projects that use autoconf to have a good ./configure
line.
BinaryBuilder.Wizard.provide_hints
— Methodprovide_hints(state::WizardState, path::AbstractString)
Given an unpacked source directory, provide hints on how a user might go about building the binary bounty they so richly desire.
BinaryBuilder.Wizard.step1
— Methodstep1(state::WizardState)
It all starts with a single step, the unabashed ambition to leave your current stability and engage with the universe on a quest to create something new, beautiful and unforeseen. It all ends with compiler errors.
This step selects the relevant platform(s) for the built binaries.
BinaryBuilder.Wizard.step2
— Methodstep2(state::WizardState)
This step obtains the source code to be built and required binary dependencies.
BinaryBuilder.Wizard.step34
— Methodstep34(state::WizardState)
Starts initial build for Linux x86_64, which is our initial test target platform. Sources that build properly for this platform continue on to attempt builds for more complex platforms.
BinaryBuilder.Wizard.step3_audit
— Methodstep3_audit(state::WizardState, platform::AbstractPlatform, prefix::Prefix)
Audit the prefix
.
BinaryBuilder.Wizard.step3_interactive
— Methodstep3_interactive(state::WizardState, prefix::Prefix, platform::AbstractPlatform,
ur::Runner, build_path::AbstractString)
The interactive portion of step3, moving on to either rebuild with an edited script or proceed to step 4.
BinaryBuilder.Wizard.step3_retry
— Methodstep3_retry(state::WizardState)
Rebuilds the initial Linux x86_64 build after things like editing the script file manually, etc...
BinaryBuilder.Wizard.step4
— Methodstep4(state::WizardState, ur::Runner, platform::AbstractPlatform,
build_path::AbstractString, prefix::Prefix)
The fourth step selects build products after the first build is done
BinaryBuilder.Wizard.with_gitcreds
— Methodwith_gitcreds(f, username::AbstractString, password::AbstractString)
Calls f
with an LibGit2.UserPasswordCredential
object as an argument, constructed from the username
and password
values. with_gitcreds
ensures that the credentials object gets properly shredded after it's no longer necessary. E.g.:
julia with_gitcreds(user, token) do creds LibGit2.clone("https://github.com/foo/bar.git", "bar"; credentials=creds) end
`
BinaryBuilder.Wizard.yggdrasil_build_tarballs_path
— Methodyggdrasil_build_tarballs_path(name::String)
Return the relative path within an Yggdrasil clone where this project (given its name) would be stored. This is useful for things like generating the build_tarballs.jl
file and checking to see if it already exists, etc...
Note that we do not allow case-ambiguities within Yggdrasil, we check for this using the utility function case_insensitive_file_exists(path)
.
BinaryBuilder.Wizard.yggdrasil_deploy
— Functionyggdrasil_deploy(state::WizardState)
Write out a WizardState to a build_tarballs.jl
in an Yggdrasil
clone, then open a pull request against Yggdrasil
.
BinaryBuilder.Wizard.yn_prompt
— Functionyn_prompt(state::WizardState, question::AbstractString, default = :y)
Perform a [Y/n]
or [y/N]
question loop, using default
to choose between the prompt styles, and looping until a proper response (e.g. "y"
, "yes"
, "n"
or "no"
) is received.
Command Line
BinaryBuilder.build_tarballs
— Functionbuild_tarballs(ARGS, src_name, src_version, sources, script, platforms,
products, dependencies; kwargs...)
This should be the top-level function called from a build_tarballs.jl
file. It takes in the information baked into a build_tarballs.jl
file such as the sources
to download, the products
to build, etc... and will automatically download, build and package the tarballs, generating a build.jl
file when appropriate.
Generally, ARGS
should be the top-level Julia ARGS
command-line arguments object. build_tarballs
does some rudimentary parsing of the arguments. To see what it can do, you can call it with --help
in the ARGS
or see the Command Line section in the manual.
The kwargs
are passed on to autobuild
, see there for a list of supported ones. A few additional keyword arguments are accept:
julia_compat
can be set to a version string which is used to set the supported Julia version in the[compat]
section of theProject.toml
of the generated JLL package. The default value is"1.0"
.lazy_artifacts
sets whether the artifacts should be lazy.init_block
may be set to a string containing Julia code; if present, this code will be inserted into the initialization path of the generated JLL package. This can for example be used to invoke an initialization API of a shared library.augment_platform_block
may be set to a string containing Julia code; if present, this code will be inserted into the top-level of the generated JLL package. It must define a functionaugment_platform!
that takes as a single argument, the target platform and returns the target platform, with amended tags. This augmented platform will then be used by the JLL wrapper to select the artifact. Note that this option requires the Julia compatibilityjulia_compat
to be 1.6 or higher.validate_name
ensures thatsrc_name
constitutes a valid Julia identifier. Since the generated JLL package is named according tosrc_name
, this should only be set tofalse
if you really know what you're doing.
The init_block
and augment_platform_block
keyword arguments are experimental and may be removed in a future version of this package. Please use them sparingly.
The build_tarballs
function also parses command line arguments. The syntax is described in the --help
output:
Usage: build_tarballs.jl [target1,target2,...] [--help]
[--verbose] [--debug]
[--deploy] [--deploy-bin] [--deploy-jll]
[--register] [--meta-json]
Options:
targets By default `build_tarballs.jl` will build a tarball
for every target within the `platforms` variable.
To override this, pass in a list of comma-separated
target triplets for each target to be built. Note
that this can be used to build for platforms that
are not listed in the 'default list' of platforms
in the build_tarballs.jl script.
--verbose This streams compiler output to stdout during the
build which can be very helpful for finding bugs.
Note that it is colorized if you pass the
--color=yes option to julia, see examples below.
--debug=<mode> This causes a failed build to drop into an
interactive shell for debugging purposes. `<mode>`
can be one of `error`, `begin` or `end`. `error`
drops you into the interactive shell only when there
is an error during the build, this is the default
when no mode is specified. `begin` forces an error
at the beginning of the build, before any command in
the script is run. `end` forces an error at the end
of the build script, useful to debug a successful
build for which the auditor would fail.
--deploy=<repo> Deploy binaries and JLL wrapper code to a github
release of an autogenerated repository. Uses
`github.com/JuliaBinaryWrappers/<name>_jll.jl` by
default, unless `<repo>` is set, in which case it
should be set as `<owner>/<name>_jll.jl`. Setting
this option is equivalent to setting `--deploy-bin`
and `--deploy-jll`. If `<repo>` is set to "local"
then nothing will be uploaded, but JLL packages
will still be written out to `~/.julia/dev/`.
--deploy-bin=<repo> Deploy just the built binaries
--deploy-jll=<repo> Deploy just the JLL code wrappers
--register=<depot> Register into the given depot. If no path is
given, defaults to `~/.julia`. Registration
requires deployment of the JLL wrapper code, so
so using `--register` without `--deploy` or the
more specific `--deploy-jll` is an error.
--skip-build Skips building the platform binaries. This option
is useful if, e.g., you have already built all
platform binaries and now only wish to deploy the
JLL package to GitHub. Note that this will error if
not all tarballs for the listed platforms are
present.
--meta-json Output a JSON representation of the given build
instead of actually building. Note that this can
(and often does) output multiple JSON objects for
multiple platforms, multi-stage builds, etc...
--skip-audit Skips auditing of the output products.
--help Print out this message.
Examples:
julia --color=yes build_tarballs.jl --verbose
This builds all tarballs, with colorized output.
julia build_tarballs.jl x86_64-linux-gnu,i686-linux-gnu
This builds two tarballs for the two platforms given, with a
minimum of output messages.
Supported Platforms:
aarch64-apple-darwin
aarch64-linux-gnu
aarch64-linux-musl
aarch64-unknown-freebsd
armv6l-linux-gnueabihf
armv6l-linux-musleabihf
armv7l-linux-gnueabihf
armv7l-linux-musleabihf
i686-linux-gnu
i686-linux-musl
i686-w64-mingw32
powerpc64le-linux-gnu
x86_64-apple-darwin
x86_64-linux-gnu
x86_64-linux-musl
x86_64-unknown-freebsd
x86_64-w64-mingw32