|
1 |
| -# fmod-sys |
2 |
| - |
3 |
| -Bindgen generated wrappers for FMOD |
4 |
| - |
5 |
| -This library is aiming to be an idiomatic "-sys" version of wrappers for [FMOD](https://fmod.com). |
6 |
| - |
7 |
| -The library itself is licensed using the [MIT license](./LICENSE), but the `fmodapi` folder contains headers from the FMOD API download, and those files are licensed under the [FMOD License](./fmodapi/LICENSE.TXT). |
8 |
| - |
9 |
| -# Usage |
10 |
| - |
11 |
| -You **MUST** register your product with FMOD and comply with their licensing terms before shipping your commercial product. |
12 |
| - |
13 |
| -While I'm still getting this testing, you can use the `git` feature of Cargo.toml dependencies to use this crate: |
14 |
| - |
15 |
| -```toml |
16 |
| -[dependencies] |
17 |
| -fmod-sys = { git = "https://github.com/jestarray/fmod-sys.git" } |
18 |
| -``` |
19 |
| - |
20 |
| -You will need to put the fmod libraries in the root directory of your project. |
21 |
| - |
22 |
| -# Enabling Studio APIs |
23 |
| - |
24 |
| -By default, the core library and its API is all that is exported. If you want to enable the FMOD Studio API, enable the `studio` feature: |
25 |
| - |
26 |
| -```toml |
27 |
| -[dependencies] |
28 |
| -fmod-sys = { git = "https://github.com/jestarray/fmod-sys.git", features = ["studio"] } |
29 |
| -``` |
30 |
| - |
31 |
| -# Enabling Debug logging features of fmod |
32 |
| - |
33 |
| -```toml |
34 |
| -[dependencies] |
35 |
| -fmod-sys = { git = "https://github.com/jestarray/fmod-sys.git", features = ["Debug"] } |
36 |
| -``` |
37 |
| - |
38 |
| - |
39 |
| -# Building |
40 |
| - |
41 |
| -To update the headers, just copy them into the fmodapi folder, make sure the LICENSE.TXT doesn't need to be updated, and then the build.rs script should automatically generate the new bindings. |
42 |
| - |
43 |
| -## Mac OS Notes |
44 |
| - |
45 |
| -When attempting to run an application linking against libfmod.dylib without signing it, you will be prompted for a security warning. Find the file in the Finder, right click on it and choose Open. It makes no sense to do this, but it will prompt you just like it would an unsigned application -- Click open and it will launch the Terminal app and do nothing. |
46 |
| - |
47 |
| -However, once you've done this step, you can run the application until you replace the library wth a new version. |
48 |
| - |
49 |
| -# todo |
50 |
| -- put all the fmod.dlls into a lib folder. For some reason I can't get bindgen to look in the folder(seems like we cant really for windows?) |
| 1 | +# fmod-sys |
| 2 | + |
| 3 | +Bindgen generated wrappers for FMOD |
| 4 | + |
| 5 | +This library is aiming to be an idiomatic "-sys" version of wrappers for [FMOD](https://fmod.com). |
| 6 | + |
| 7 | +The library itself is licensed using the [MIT license](./LICENSE), but the `fmodapi` folder contains headers from the FMOD API download, and those files are licensed under the [FMOD License](./fmodapi/LICENSE.TXT). |
| 8 | + |
| 9 | +# Usage |
| 10 | + |
| 11 | +You **MUST** register your product with FMOD and comply with their licensing terms before shipping your commercial product. |
| 12 | + |
| 13 | +While I'm still getting this testing, you can use the `git` feature of Cargo.toml dependencies to use this crate: |
| 14 | + |
| 15 | +```toml |
| 16 | +[dependencies] |
| 17 | +fmod-sys = { git = "https://github.com/jestarray/fmod-sys.git" } |
| 18 | +``` |
| 19 | + |
| 20 | +You will need to put the fmod libraries in the root directory of your project. |
| 21 | + |
| 22 | +# Enabling Studio APIs |
| 23 | + |
| 24 | +By default, the core library and its API is all that is exported. If you want to enable the FMOD Studio API, enable the `studio` feature: |
| 25 | + |
| 26 | +```toml |
| 27 | +[dependencies] |
| 28 | +fmod-sys = { git = "https://github.com/jestarray/fmod-sys.git", features = ["studio"] } |
| 29 | +``` |
| 30 | + |
| 31 | +# Enabling Debug logging features of fmod |
| 32 | + |
| 33 | +```toml |
| 34 | +[dependencies] |
| 35 | +fmod-sys = { git = "https://github.com/jestarray/fmod-sys.git", features = ["Debug"] } |
| 36 | +``` |
| 37 | + |
| 38 | + |
| 39 | +# Building |
| 40 | + |
| 41 | +To update the headers, just copy them into the fmodapi folder, make sure the LICENSE.TXT doesn't need to be updated, and then the build.rs script should automatically generate the new bindings. |
| 42 | + |
| 43 | +## Mac OS Notes |
| 44 | + |
| 45 | +When attempting to run an application linking against libfmod.dylib without signing it, you will be prompted for a security warning. Find the file in the Finder, right click on it and choose Open. It makes no sense to do this, but it will prompt you just like it would an unsigned application -- Click open and it will launch the Terminal app and do nothing. |
| 46 | + |
| 47 | +However, once you've done this step, you can run the application until you replace the library wth a new version. |
| 48 | + |
| 49 | +## Windows Notes: |
| 50 | +The `_vc` suffix on the `.lib` files for windows need to be removed. Stick all the `.dll` and `.lib` in the root folder of your project. For shipping your game you only need to include `fmod.dll` and `fmodstudio.dll` |
| 51 | + |
| 52 | +## Linux Notes: |
| 53 | +For linux you may need to tell rust where to look for the libfmod files. Add where to find it in `.bash_profile` |
| 54 | +`export LD_LIBRARY_PATH="PATH/TO/FMODLIBS"` |
| 55 | + |
| 56 | +# todo |
| 57 | +- put all the fmod.dlls into a lib folder. For some reason I can't get bindgen to look in the folder(seems like we cant really for windows?) |
51 | 58 | - examples
|
0 commit comments