1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
//! Raw FFI bindings for the Epic Online Services (EOS) C SDK.
//!
//! `eos-sys` is the low-level layer in the EOS Rust stack:
//!
//! - `eos-sys`: raw, mostly 1:1 C bindings
//! - `eos-rs`: higher-level safe wrappers built on top of `eos-sys`
//!
//! # Setup
//!
//! This crate does not bundle the EOS SDK binaries.
//! You must provide the SDK root directory via:
//!
//! - `EOS_SDK_DIR=/path/to/EOS-SDK`
//!
//! The directory must contain:
//!
//! - `Include/`
//! - `Lib/`
//!
//! On Windows, your final application also needs `EOSSDK-Win64-Shipping.dll`
//! next to the executable at runtime.
//!
//! # Why No LLVM Requirement
//!
//! This crate intentionally ships pre-generated bindings in-source, so downstream
//! users do not need LLVM/clang installed to compile.
//!
//! If you maintain bindings and want to regenerate them, build with:
//!
//! `cargo build -p eos-sys --no-default-features --features bindgen`
//!
//! # Safety
//!
//! This crate exposes raw FFI APIs and raw pointers/handles from EOS. Callers are
//! responsible for:
//!
//! - pointer validity,
//! - callback lifetime correctness,
//! - calling the correct EOS `*_Release` APIs.
//!
//! For safer ownership/lifetime behavior, prefer `eos-rs` where possible.
pub use ;
// By default we ship pre-generated bindings so downstream users don't need LLVM/clang.
// If you need to regenerate: build with `--features eos-sys/bindgen`.
pub use *;
include!;