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
{{ message }}
Repository navigation
macOS builds failing with "unexpected cfg condition value: cargo-clippy" #229
I think that ideally Baseview would just switch to the objc2 crate, but that would require a decent amount of work since it's not a drop-in replacement. The simpler workaround for now would probably be to point at the master branch of the rust-objc repo, since a fix for the issue has been merged but was never published to crates.io.
Happy to help with either, or with the objc2 migration.
UPD: just in case, to speed things up, filed a PR with that fix: #231.
UPD2: Filed #232 with the objc2 macros-only migration; supersedes #231. Kept cocoa for framework type bindings to leave the bigger cocoa-replacement decision open, since you flagged that direction. PR also folds in fixes for several latent @encode and NSException traps the stricter objc2 verification surfaces.
Activity
micahrj commentedon Apr 24, 2026
I gave this a try and ran into the issue that the
cocoacrate also depends on theobjccrate, so the workaround would require forkingcocoaas well.paravozz commentedon Apr 24, 2026
@micahrj
I dug into this earlier, tested a small
build.rsworkaround that silences the warning locally:Happy to help with either, or with the
objc2migration.UPD: just in case, to speed things up, filed a PR with that fix: #231.
UPD2: Filed #232 with the
objc2macros-only migration; supersedes #231. Keptcocoafor framework type bindings to leave the bigger cocoa-replacement decision open, since you flagged that direction. PR also folds in fixes for several latent@encodeandNSExceptiontraps the stricter objc2 verification surfaces.micahrj commentedon Apr 25, 2026
It looks like we already had
#![allow(unexpected_cfgs)]attributes in the relevant modules, but for some reason they have stopped working:baseview/src/macos/mod.rs
Line 3 in 237d323
baseview/src/gl/macos.rs
Line 3 in 237d323
I've found that if I move the attribute to the crate root it successfully silences the warning again: #233