gr

Crates.iogr
lib.rsgr
version
sourcesrc
created_at2015-12-19 17:58:50.300398
updated_at2024-10-09 09:47:20.257562
descriptionRust wrapper for the GR framework
homepagehttps://gr-framework.org
repositoryhttps://github.com/rust-gr/grs.git
max_upload_size
id3705
Cargo.toml error:TOML parse error at line 19, column 1 | 19 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include`
size0
owners (github:rust-gr:owners)

documentation

README

GR - a universal framework for visualization applications

Screenshots

GR is essentially based on an implementation of a Graphical Kernel System (GKS) and OpenGL. As a self-contained system it can quickly and easily be integrated into existing applications.

The GR framework can be used in imperative programming systems or integrated into modern object-oriented systems, in particular those based on GUI toolkits. GR is characterized by its high interoperability and can be used with modern web technologies. The GR framework is especially suitable for real-time or signal processing environments.

GR was developed by the Scientific IT-Systems group at the Peter Grünberg Institute at Forschunsgzentrum Jülich. The main development has been done by Josef Heinen who currently maintains the software, but there are other developers who currently make valuable contributions. Special thanks to Florian Rhiem (GR3) and Christian Felder (qtgr, setup.py).

For further information please refer to the GR home page.

Using the GR Rust-crate

  1. Install GR
  2. Set the GRLIB environment variable to the path of GR's lib directory / folder
    • It should contain .lib, .dylib or .so files
    • On Windows (and also MinGW) you should use an absolute path
    • On Linux and Mac some paths will be searched when GRLIB doesn't refer to a usable installation:
      • ~/gr (ie. implicit GRLIB=~/gr/lib)
      • /usr/gr (ie. implicit GRLIB=/usr/gr/lib)
      • /usr/local/gr (ie. implicit GRLIB=/usr/local/gr/lib)
    • This variable is only needed at compile-time
  3. The crate's build-script outputs a path as cargo:lib_dir
    • The Rust program will need to load libraries from that path! Make it accessible!
      You may want to put this into your PATH (Windows), LD_LIBRARY_PATH (Linux), DYLD_LIBRARY_PATH (Mac) or your binaries' rpaths.
    • On Windows this is not the same as GRLIB!
      It will point to the bin folder, which contains the .dlls.

To test your setup, try compiling and running this simple application:

use gr::gr;
use std::io::{stdin, Read};

fn main() {
    gr::polyline(2, &[0.0, 1.0], &[0.0, 1.0]).unwrap();
    gr::updatews();
    stdin().bytes().next();
}

License

Licensed under MIT license (LICENSE or http://opensource.org/licenses/MIT)

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, shall be licensed as above, without any additional terms or conditions.

Commit count: 250

cargo fmt