Divert icon indicating copy to clipboard operation
Divert copied to clipboard

Published 20 hours ago • verified publisher icon basil00

Build for Windows RT (ARMv7)

Open ValdikSS opened this issue 7 years ago • 6 comments

Hi, a user of GoodbyeDPI asking for Windows RT (8.1 ARMv7) build. He says that his device is jailbroken, with administrator privileges, and that it also loads drivers (e.g. VueScan). https://github.com/ValdikSS/GoodbyeDPI/issues/51

Is it possible to compile WinDivert for Windows RT? Is it possible to sign driver with the current signing key, are there any architecture restrictions?

ValdikSS avatar Jan 11 '18 17:01 ValdikSS

In principle it should be possible. I think the main problem is that WinDivert currently uses WDK 7.1 and I don't think that version supports ARM cpus.

basil00 avatar Jan 12 '18 01:01 basil00

Hi there. It's for my request issue. Why dontcha switch to WDK8.1? I suppose WDK7.1 isn't support Win8.x well at all (except order of compatibility with lower Windows version)

hooddy avatar Jan 12 '18 05:01 hooddy

WinDivert needs to support Windows 7 and up, and the easiest way to accomplish this is to use WDK7.

That doesn't mean other WDKs couldn't also be supported side-by-side. But there hasn't been any need to do so yet.

Also, I'd prefer if the driver build could be wrapped up into a script like the current wddk-build.bat. Newer WDKs integrate into VS I believe, which complicates the build process. For example, I recently tried to build the WFPSampler drivers. Attempting to follow the instructions, I first had to install VS, then install WDK 10 extensions, then change a bunch of config options in the GUI for some reason, and (after several tries) it finally built a non-functional executable. I'm sure there is some config option somewhere that is wrong, but at this point I'd had enough and gave up.

basil00 avatar Jan 12 '18 06:01 basil00

Well ok... In this case I really doubt its possible to build ARM driver under WDK7.1. Thanks

hooddy avatar Jan 12 '18 06:01 hooddy

Well, as I said, WDK8 or WDK10 could be supported in addition to WDK7. This is not my priority at the moment, but others are welcome to work on it if they want to.

basil00 avatar Jan 12 '18 06:01 basil00

  1. GoodbyeDPI fails to build with current master. Support for the arm architecture would require support for Windivert's latest API (1.4) first.

  2. Switching to a higher version of the WDK would mean switching to a higher Windows SDK as well. See the 1.4 wishlist.

  3. Has anyone ever tried targeting arm (universal runtime) before? Basil said that it should be possible. The universal runtime is a completely different animal I argue.

On Jan 12, 2018, at 8:11 AM, hooddy [email protected] wrote:

Hi there. It's for my request issue. Why dontcha switch to WDK8? I suppose WDK7 isnt support Win8 well at all.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

sgeto avatar Jan 12 '18 18:01 sgeto