Windows gcc verson

[dxls168]

Hi:
I have tried to compile your project with MINGW and have solved all the compilation warnings and errors, but the final project still does not work and the program stuck in the crack process.
In Ubuntu, the program is very easy to use.
Sincerely hope that you can out of a windows version of the project, very grateful to you.

[aczid]

Hey, I'm sorry but I don't think this will really work again. There is no up-to-date libnfc.dll as far as I can tell.

[iWhacko]

I just built the libnfc.dll from source?

[dxls168]

solve_bs is enough.Not need libnfc.

[aczid]

I had trouble building the latest libnfc.dll. Anyway I'm not sure why it doesn't work when compiled on windows.

[dxls168]

Hi,You can use cmake to build it.Then use gcc .Can you give me an e-mail address?I can send you lib and dll.

[iWhacko]

crypto1_bs_crack.c uses sysinfo.h etc and some linux specific calls for memory. I'm not familiar enough with it that I can port it to windows. However I added the dll etc to this post maybe it's of use to you for testing
libnfc.zip

[aczid]

I did a bit more investigation. The problem I'm having is combining a 32 bit-library (libnfc) with some 64-bit code (crypto1_bs/crapto1/craptev1).

[aczid]

After some more small patches, I've tested a linux/mingw cross-compiled versions of solve_piwi and solve_piwi_bs for 32-bit windows in a win7 VM and they both work fine for me. No detection of the number of CPU cores yet, though. And also I did not get these versions working on native win8 for some reason...
Added make targets 'win32' and 'win64' for these. If anything it's evidence the code works on windows in principle.

[dxls168]

I'll try!
Thank you again for your great help!

[dxls168]

Perfect!
Thanks again!

[aczid]

Wow, I didn't get libnfc code to work when cross-compiling. Thank you for testing, that's even better than I had hoped!

[aczid]

What build system are you using? You're very welcome to add native (non-mingw) targets to the Makefile and file a pull request. Feel free to rename the mingw cross-compilation make targets while you are at it.

[aczid]

I assume you also had to replace some of the signal()/alarm() calls to use windows-style Timers? I have an untested patch for libnfc_crypto1_bs.c for that, too.

[maxben14]

dxls168, write please how compile crypto1_bs on windows platform.

[dxls168]

1.You need download the Mingw .
2.Put the files into the ’user‘ folder.
3 Run the Mingw-shell and into the ’user‘ folder,then input the command 'make' .
4 If anything get wrong,change the Makefile chose one to make.

[maxben14]

dxls168, can send me win exe file compiled please ?

[aczid]

Bla's license clearly states no redistribution. Don't be lazy.

[marcoxx888]

hi dxls168, may I have some tips to get crypto1_bs compiled for Windows?
My emal is marco.rossinol at gmail . com

[briggeml]

Hi @dxls168, I also compiled crypto1_bs for Win, but still couldn't get keys despite the long time passed. What did you do with (Mingw warning and errors):

1. thread_count = get_nprocs_conf();? //hardcoded threads?
2. alarm(1); signal(SIGALRM, notify_status_offline);? //some kind of: timeSetEvent(0, 0, notify_status_offline, 0, TIME_PERIODIC);?
3. fcntl(0, F_SETFL, O_NONBLOCK);? //unsigned long on = 1; ioctlsocket(0, FIONBIO, &on);?

[dxls168]

Hi @briggeml:
These are Linux functions.You can ignore progress display and set the thread_count =1.

[Semen8991]

Hi @briggeml:
These are Linux functions.You can ignore progress display and set the thread_count =1.

Hello! Can you please help with compiling on Windows?