-
-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug : wrong type conversions making compilation on poppler-rs fail on windows #1605
Comments
The code generator is generating it as |
No, this is a gir bug. The gir was updated to contain the commit you mentioned and if you check the ffi function below pub fn poppler_document_set_modification_date(
document: *mut PopplerDocument,
modification_date: time_t,
); it is generated correctly. Although, the safe wrapper is generated using #[doc(alias = "poppler_document_set_modification_date")]
pub fn set_modification_date(&self, modification_date: libc::c_long) {
unsafe {
ffi::poppler_document_set_modification_date(self.to_glib_none().0, modification_date);
}
} |
never mind, it was actually the gir file that was outdated. |
Copy of https://gitlab.gnome.org/World/Rust/poppler-rs/-/issues/1
Downstream
poppler_rs
cannot compile because of a type mismatch on windows (on one side alibc::clong
that is i32 on windows and on the other side the type oftime_t
that is seen as i64).According to bilelmoussaoui the type issue comes from this repo and types conversions : https://gitlab.gnome.org/World/Rust/poppler-rs/-/issues/1#note_2242804
The text was updated successfully, but these errors were encountered: