You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For this issue one should look at how rapier does it: https://github.com/dimforge/rapier
And basically it needs in salva multiple packages exported, similar to how rapier has. So right now this exports salva2d and salva3d, it would need salva2d-f64 and salva3d-f64. Each of these would be defined in the Cargo.toml file and then there would be a define for the precision:
So in the build directory of salva there would be 2 new folders, salva2d-f64 and salva3d-f64. Then in github workflows there needs to be automatic building (and deploying?) of the new packages.
Activity
Ughuuu commentedon Oct 9, 2024
For this issue one should look at how rapier does it: https://github.com/dimforge/rapier
And basically it needs in salva multiple packages exported, similar to how rapier has. So right now this exports salva2d and salva3d, it would need salva2d-f64 and salva3d-f64. Each of these would be defined in the
Cargo.tomlfile and then there would be a define for the precision:So in the build directory of salva there would be 2 new folders, salva2d-f64 and salva3d-f64. Then in github workflows there needs to be automatic building (and deploying?) of the new packages.
Example of how to use the f32 and f64 flags:
Ughuuu commentedon Jun 27, 2026
Also fixed by latest PR. #69 (aside for publishing to crates.io).