please have a good day
An opinionated set of "high level" wrappers for the fermium SDL2 bindings.
There are examples available if you want to see it in action.
unsafe
code, and that's all there is to
it. I can't cover up every dangerous possibility for you. I don't really
consider this a major drawback, but you might think differently. I still try
to keep the unsafe
to a minimum of course.Obviously this uses SDL2. The fermium crate is used as the bindings crate. You will need version 2.0.9 or later:
fermium
, you
don't need to do any special setup at all.-fPIC
flag enabled in your SDL2 install! This is necessary
because the build will static link to SDL2 by default.sudo
for a default install (to /usr/local/lib
)
or adjust it to fit your needs. Linux programmer are all pros, right?cargo clean
to make the build.rs
work.You'll probably want to set the window_subsystem to "windows" in your beryllium programs. Just add this to the top of the main file of any binary or example:
```rust
```
Note that we only want it enabled when debug_assertions
are not active. If
it's configured you don't have a default console at all so you can't print
debug messages. We only need to set it with the version we plan to ship to
users.
This line won't have any effect on the build outside Windows, so no worries.
This crate uses the Zlib license, the same license that SDL2 itself uses.
PLEASE DO NOT PR TO MASTER
All new development goes to a
dev branch. Updates are only
transferred to the master
branch when it's time to do a new release to
crates.io.
Some call it odd, but I just like having the master
branch always reflect the
latest available on crates.io whenever possible to keep confusion to a minimum
when jumping between the two websites.