Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Arrayfire Rust Bindings
ArrayFire is a high performance library for parallel computing with an easy-to-use API. It enables users to write scientific computing code that is portable across CUDA, OpenCL and CPU devices. This project provides Rust bindings for the ArrayFire library. The wrapper is currently compliant with ArrayFire 3.2 API. If you find any bugs, please report them here.
Documentation
You can find the most recent updated documentation here.
Build
Edit build.conf to modify the build flags. The structure is a simple JSON blob. Currently Rust does not allow key:value pairs to be passed from the CLI. To use an existing ArrayFire installation modify the first three JSON values. You can install ArrayFire using one of the following two ways.
To build arrayfire submodule available in the rust wrapper, you have to do the following.
This is recommended way to build Rust wrapper since the submodule points to the most compatible version of ArrayFire the Rust wrapper has been tested with. You can find the ArrayFire dependencies below.
Operating System Support: Currently, only Linux and OSX. With Rust 1.4(MSVC binary), we soon expect to get the Windows support available.
Example
let num_rows: u64 = 5;
let num_cols: u64 = 3;
let dims = new;
println!;
let a = match randu ;
print;
Sample output
)
Issues
You might see something along the lines of :
You need to add the location of libaf.{dylib, so, dll} to your LD_LIBRARY_PATH.
Note
This is a work in progress and is not intended for production use.
Acknowledgements
The ArrayFire library is written by developers at ArrayFire LLC with contributions from several individuals.
The developers at ArrayFire LLC have received partial financial support from several grants and institutions. Those that wish to receive public acknowledgement are listed below:
Grants
This material is based upon work supported by the DARPA SBIR Program Office under Contract Numbers W31P4Q-14-C-0012 and W31P4Q-15-C-0008. Any opinions, findings and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the DARPA SBIR Program Office.