Skip to content
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

Build for Windows RT (ARMv7) #115

Open
ValdikSS opened this issue Jan 11, 2018 · 6 comments
Open

Build for Windows RT (ARMv7) #115

ValdikSS opened this issue Jan 11, 2018 · 6 comments

Comments

@ValdikSS
Copy link

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).
ValdikSS/GoodbyeDPI#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?

@basil00
Copy link
Owner

basil00 commented Jan 12, 2018

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.

@hooddy
Copy link

hooddy commented Jan 12, 2018

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)

@basil00
Copy link
Owner

basil00 commented Jan 12, 2018

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.

@hooddy
Copy link

hooddy commented Jan 12, 2018

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

@basil00
Copy link
Owner

basil00 commented Jan 12, 2018

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.

@sgeto
Copy link

sgeto commented Jan 12, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants