Author JuliaBinaryWrappers
0 Stars
Updated Last
3 Years Ago
Started In
February 2020


This is an autogenerated package constructed using BinaryBuilder.jl.


The code bindings within this package are autogenerated from the following Products defined within the build_tarballs.jl file that generated this package:

products = [
    ExecutableProduct(["aiginfo"], :aiginfo),
    ExecutableProduct(["aigsplit"], :aigsplit),
    ExecutableProduct(["aigtoblif"], :aigtoblif),
    ExecutableProduct(["aigmiter"], :aigmiter),
    ExecutableProduct(["bliftoaig"], :bliftoaig),
    ExecutableProduct(["aigand"], :aigand),
    ExecutableProduct(["aigfuzz"], :aigfuzz),
    ExecutableProduct(["aigtocnf"], :aigtocnf),
    ExecutableProduct(["aigtodot"], :aigtodot),
    ExecutableProduct(["smvtoaig"], :smvtoaig),
    ExecutableProduct(["wrapstim"], :wrapstim),
    ExecutableProduct(["aigreset"], :aigreset),
    ExecutableProduct(["aigstrip"], :aigstrip),
    ExecutableProduct(["aigtosmv"], :aigtosmv),
    ExecutableProduct(["aigmove"], :aigmove),
    ExecutableProduct(["aigsim"], :aigsim),
    ExecutableProduct(["andtoaig"], :andtoaig),
    ExecutableProduct(["soltostim"], :soltostim),
    ExecutableProduct(["aigunroll"], :aigunroll),
    ExecutableProduct(["aigtoaig"], :aigtoaig),
    ExecutableProduct(["aigunconstraint"], :aigunconstraint),
    ExecutableProduct(["aigdd"], :aigdd),
    ExecutableProduct(["aigflip"], :aigflip),
    ExecutableProduct(["aigor"], :aigor),
    ExecutableProduct(["aignm"], :aignm),
    ExecutableProduct(["aigjoin"], :aigjoin)

Usage example

For example purposes, we will assume that the following products were defined in the imaginary package Example_jll:

products = [
    FileProduct("src/data.txt", :data_txt),
    LibraryProduct("libdataproc", :libdataproc),
    ExecutableProduct("mungify", :mungify_exe)

With such products defined, Example_jll would contain data_txt, libdataproc and mungify_exe symbols exported. For FileProduct variables, the exported value is a string pointing to the location of the file on-disk. For LibraryProduct variables, it is a string corresponding to the SONAME of the desired library (it will have already been dlopen()'ed, so typical ccall() usage applies), and for ExecutableProduct variables, the exported value is a function that can be called to set appropriate environment variables. Example:

using Example_jll

# For file products, you can access its file location directly:
data_lines = open(data_txt, "r") do io

# For library products, you can use the exported variable name in `ccall()` invocations directly
num_chars = ccall((:count_characters, libdataproc), Cint, (Cstring, Cint), data_lines[1], length(data_lines[1]))

# For executable products, you can use the exported variable name as a function that you can call
mungify_exe() do mungify_exe_path
    run(`$mungify_exe_path $num_chars`)