iOS-DeviceSupport VS windows-rs

Since we want to deploy to iOS 15.7, we will need the Device Support files for this iOS version. Head to https://github.com/iGhibli/iOS-DeviceSupport and download DeviceSupport/15.7(FromXcode_14.1_Release_Candidate_xip).zip, unzip this file in Finder, then move the folder 15.7 to /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport.

They take forever but it’s only once in a while. If you’re just trying to support newer iOS versions you can just yank them from here instead of updating.

https://github.com/iGhibli/iOS-DeviceSupport

Use something like https://github.com/iGhibli/iOS-DeviceSupport to get the device support files, and https://pmbaty.com/iosbuildenv/ to develop apps

To get around this, you can download the iOS Device Support file corresponding to your iOS version from https://github.com/iGhibli/iOS-DeviceSupport and paste it to the following directory:

Instead of upgrading Xcode, I used to just bring over the new device support files for newer iOS versions: https://github.com/iGhibli/iOS-DeviceSupport

Is there any place I can find device support files for iOS 14.7 to be used with XCode 12.0.1? I cannot find it in places like https://github.com/iGhibli/iOS-DeviceSupport/tree/master/DeviceSupport . Is it because the release is too new?

I'd say Rust does have that big ticket ecosystem push. Microsoft has been embracing Rust lately, with things like official Windows bindings [1].

The bigger problem is just inertia: large game engines are enormous.

[1]: https://github.com/microsoft/windows-rs

It's a shame that, unlike with Win32, using WinUI places pretty harsh restrictions on which programming languages and environments you can use. Only C# and C++ are supported, the latter only with Microsoft compilers. For everything else, including Rust[1], Python and MinGW C/C++, there is no answer for OP's question, and the effect of this on the visual consistency of the Windows desktop is obvious - there is none. Every third-party app uses a different toolkit with a different look and feel, because the library providing the standard look and feel simply isn't available to the majority of developers.

[1]: https://github.com/microsoft/windows-rs/pull/1836

[0] https://github.com/microsoft/windows-rs

On Windows you'd need to call the LoadLibraryEx method. You'd also need a crate to call Win32 functions, I suggest windows-rs.

windows-rs, Microsoft's crate wrapping the Windows API, already includes the WDK, the special sdk for creating kernel code.

On windows, I'll probably use https://github.com/gabdube/native-windows-gui or https://github.com/microsoft/windows-rs both of them seem pretty solid.

*nod* It's an official Microsoft thing generated from official Microsoft API definition files. (The repo is at microsoft/windows-rs on GitHub.)

Microsoft offers official "bindings" to Win32 APIs through win32metadata. However, until recently, it did not include metadata for kernel-level functions or WDK. In early 2021, an issue was raised through windows-rs regarding this limitation, but progress was slow until now. Microsoft has finally released official metadata for WDK, which can be found on the wdkmetadata repository. The latest comment on the issue thread can be found here:

Is something wrong with https://github.com/deviceplug/btleplug or you haven't found it? You could also use bindings to platform libraries like https://github.com/microsoft/windows-rs and https://github.com/rust-mobile/ndk if btleplug doesn't have something fundamental to you.