windows-drivers VS cxx

Drivers can be found here for windows installation: https://github.com/system76/windows-drivers

Hello, last week I bought a Gazelle (gaze18) and in the brief time I have had it, I've been loving it. So far everything on the laptop works out of the box in Pop!_OS (even the Nvidia drivers). However, due to some needs, I need to dual-boot Windows 10. I followed the System76 docs for installing Windows, but during the installation, the trackpad didn't work due to a lack of drivers. However, after the installation, Windows was able to install most drivers via the Windows update including the drivers for the Integrated Iris GPU. Following the driver installation part of the docs, the Intel Driver Update Utility was able to install a good amount of Intel Drivers. The docs links a git repo from s76 containing Windows drivers for laptops with open firmware+ec. However the gaze18 was not listed, I assume as its very recent. However I was able to install chipset drivers from Intel Website for Raptor Lake and I used the HID, SerialIO for the gaze17 they worked fine and the trackpad was working now that the SPI device worked. Where the issue arose when installing Nvidia Drivers.

I don't know if Windows would automatically find the drivers for the open firmware and EC that the gaze16 uses, but you can get them here: https://github.com/system76/windows-drivers

I have a System76 galp5. It's fairly thin and lightweight. I have mixed feelings about it. Linux support is good. But Windows support is pretty bad. All available drivers are here: https://github.com/system76/windows-drivers but even after installing everything in that repo listed under galp5, I still have a ton of issues including laptop not going to sleep when lid is closed, touchpad occasionally not working until I toggle it on/off from settings, etc. Getting Windows working from Pop OS using Virtual Box was also a massive, fragile headache. I would get it working, but then sometimes when using Visual Studio from inside virtual box it would freeze and the VM would be permanently bricked unless I had previously saved a snapshot.

All this to say that if you care about Linux and only Linux, System76 could be a good choice. But if you need to use Windows at all, I would steer clear of S76 until their Windows support is a little better (also YMMV - I've just had so many issues with Windows on a galp5, but that might not be the case with other models).

As the title says, I am having issues with getting windows 10(secondary OS) to work on my system76 laptop, with PopOS! (Being the primary OS). Both the keyboard and the wifi/ethernet connections do not work in Windows 10. I have already checked this github repository: https://github.com/system76/windows-drivers

Thanks for the response. Turns out I never successfully installed the provided windows thunderbolt drivers and I still haven't been able to. I noticed a rejected PR on the github containing their windows drivers reporting a similar issue and I left a comment. Please let me know if you have any thoughts! https://github.com/system76/windows-drivers/pull/10

In addition, did you manage to get the drivers for it to work fully? I asked because System76 has this: https://github.com/system76/windows-drivers

System76 Windows drivers can be found here: https://github.com/system76/windows-drivers And install directions can be found here: https://support.system76.com/articles/windows

There are cxx and autocxx, what else do you propose to do?

I would like to see a comparison of how this compares to Rust. In terms of interoperability it has Cxx (https://cxx.rs) to offer safe bindings to C++ but also has great support for Android, Linux and many other systems. You don't even need to hack together Windows bindings (as explained in the blog post) because Microsoft offers official bindings (https://crates.io/crates/windows). I'm not sure if I'd call it a superpower if any potential interoperability has to be written to be used (compared to it already being available). Or rather, in comparison to what is interoperability a Swift superpower? Certainly not C++ or C which can be used in a far wider set of targets.

We selected Qt as a cross-platform solution. The C++/Rust interface is the clunkiest and ugliest part of the application, and rather complex because some state is shared between several windows in the GUI and several threads in the backend, and any component might modify that state at any time, and updates have to be transmitted to the other components without introducing inconsistencies. Using cxx [1] helped a little, though.

The project began in 2020, and I'm not sure what I'd choose as a GUI framework today – definitely not Qt Widgets, though.

[1] https://cxx.rs/

If the build process for the C library isn't too involved I recommend using cxx bridge (https://cxx.rs/) and letting cargo handle the build and linking. cxx basically allows you to describe the bidirectional interface (although it sounds like you only need 1 direction, which is fine too) in Rust code and it provides a "good enough" API for compiling C code inside the build.rs file.

The tooling for the first kind -- calling Rust from another language -- is a bit less developed, and tends to rely on code generation that doesn't necessarily produce a natural C API. cbindgen, uniffi, cxx, and Diplomat all take this course.

I would like to utilize OMPL's functionality in Rust code, so I want to call into OMPL C++ code somehow in Rust. I've seen two (non-mutually-exclusive) options so far: - rust-cpp, which allows you to write C++ code in Rust within the cpp!() macro. - cxx, which allows you to define both sides of the FFI boundary manually (as opposed to bindgen's automatic generation).

I'm not sure how to do this in cxx; issues like https://github.com/dtolnay/cxx/issues/447 suggest that this isn't settled yet?

I use non-vendored dependencies for the Buck build in https://github.com/dtolnay/cxx.

There's also the cpp and cxx crates for doing C++/Rust interop, but they probably aren't appropriate to use in all cases. The C ABI is definitely the safest way to go unless you're really trying to marry Rust and C++ code bases, not just writing library bindings.

There's also cxx (can't vouch for it personally but it claims to make things a lot easier) https://github.com/dtolnay/cxx