GitHub - JuliaBinaryWrappers/Fontconfig_jll.jl at 785936d816d1ae65c2a6648f3a6acbfd72535e36 (original) (raw)

Fontconfig_jll.jl

This is an autogenerated package constructed using BinaryBuilder.jl.

Products

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(["fc-conflist"], :fc_conflist), FileProduct(["etc/fonts/fonts.conf"], :fonts_conf), ExecutableProduct(["fc-cache"], :fc_cache), ExecutableProduct(["fc-query"], :fc_query), ExecutableProduct(["fc-scan"], :fc_scan), LibraryProduct(["libfontconfig"], :libfontconfig), ExecutableProduct(["fc-list"], :fc_list), ExecutableProduct(["fc-match"], :fc_match), ExecutableProduct(["fc-pattern"], :fc_pattern), ExecutableProduct(["fc-cat"], :fc_cat), ExecutableProduct(["fc-validate"], :fc_validate) ]

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 readlines(io) end

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) end