Easier usage for projects

[jmeggitt]

Could this be put on crates.io or could the binaries be included on Github? I would like to have some easy way to use this library such as being able to copy paste a dependency into the cargo.toml.

I am not completely sure where to get the sim binaries required to compile this though, and I doubt others will either without some extra documentation.

ctre-rs = "2.3.4" ctre-rs = {git = "..."}

[auscompgeek]

Once wpilib-sys is published on crates.io, I'll work on getting this published as well.

[auscompgeek]

Currently verifying that ctre 0.6.1 compiles fine with wpilib-sys 0.2.3. Uploaded ctre-sys 5.4.0 and ctre 0.6.1.

The published ctre-sys 5.4.0 will only have the CCI library for athena, as it is intended to strictly track Phoenix releases. (The code in build.rs is to accommodate for simulation libraries in Phoenix 5.8.)

I'm currently working on rearchitecting the ctre-sys crate for Phoenix 5.7 - I plan to have a separate ctre-data crate to hold structs and enums that will have serde support (as I would like to see the Configuration structs have serde support to accommodate anticipate team usage).

[auscompgeek]

Also note that currently ctre-sys will not successfully link without the WPILib HAL, as I haven't been able to find a solution to the weird NI libraries linkage situation yet (and I probably won't be able to).

[Lytigas]

If packaging and/or using static libraries in wpilib-sys where possible would make things easier, that's something I could do. I'm fairly sure the NI libraries are included on the RIO by default.

[auscompgeek]

There's no issue with wpilib-sys here - in fact a robot program should build and link fine with wpilib-sys. The problem is with the NI libraries, which WPILib has had a workaround for in the HAL since the dawn of time.

Statically linking to libwpiHal probably could break any programs that interface with the roboRIO hardware. Maybe. Looking again at WPILib's tooling, they do provide a Gradle task to build static libraries. Huh.