Help compiling windows client

asper · 2013-03-01 12:34:31

Hi guys, after sending the make command I receive (at the very end) this error compiling under windows 7:

Arm and bootloader files are compiling fine; the client compiling error does not appear using cdc branch... where should I look at to solve that error ?

Last edited by asper (2013-03-02 17:27:27)

moebius · 2013-03-01 14:18:11

There's something missing about your QT lib.

rule · 2013-03-01 14:47:12

Uploaded a new mingw-proxmark.zip. The GUI based on QT should work again!

asper · 2013-03-02 17:17:43

All is compiling fine with the new MinGW (tested r664 for both official and cdc branch) ! Thank you ! I only need explanations on how to flash the new bootloader so I can make a guide !

Stand alone windows client may require those libraries (4.5MB).

Last edited by asper (2013-03-02 17:47:22)

asper · 2013-03-02 18:05:06

Bootrom updated ! Also flashed OS and FPG... REALLY REALLY FASTER THAN OLD METHOD !!!!!!!! My fingers thank you a lot

This is my actual hw version (all flashed files form r664):

Is it possible to restore the svn version in both OS image and bootrom ?

I am making a update/flashing guide !

Last edited by asper (2013-03-02 18:05:31)

rule · 2013-03-03 08:37:02

Good to hear everything works Asper, thank you very much for testing.

I figured out why the OS/Bootrom version info is not available if you compile in Windows. The info is embedded into the firmware by a PERL script. If you don't have PERL installed, this simple fails to put any info in there.

The solution is simple, just install PERL (For windows). You can download a (32- or 64-bit) binary installation package from here:
http://strawberryperl.com/

I've updated the instructions that comes with the MinGW-proxmark.zip download, so that uses can prepare them self better before compiling on Windows.

If you want, you can make a complete windows binary snapshot package (32-bit and 64-bit version?) with all the executables, libraries, compiled os/fpga/bootrom and other necessary files (including maybe flasher_old.exe). I can put it as download in the Proxmark SVN, so Windows-users could migrate easier. At least, it is not so hard to build from scratch now in Windows, but as you know, Windows-users are much more familiar depended on binary releases

asper · 2013-03-03 09:10:40

I think you got the problem man ! In fact i receive (since a few builds) 2 perl errors (even if binaries compile fine and are working) in version.c file, here are the 2 errors screenshot:

I already have perl installed but I alsto tryed to install the strawberry perl you linked with the same (bad) results... maybe a script incompatibility with windows ?

If I manage to make all working fine I will release binaries for Win64 then I will try to compile under Win32 and If I am successfull I will release 2 different compiled versions.

If you want I am on IRC now.

Last edited by asper (2013-03-03 09:17:42)

asper · 2013-03-03 10:42:11

UPDATE:

The problem seems to be under WIndows7 64 bit (maybe all 64bit WIn versions) because .elf files are compiling fine under Windows XP 32bit.
Client binaries work fine in 32bit and 64bit systems; I mean you can compile them under Win32 and they will work under Win64 and vice versa.

Here is a full r664 Windows release (.elfs+.exes+README+old bootloader flashing guide)

Last edited by asper (2013-03-03 10:50:13)

rule · 2013-03-03 14:07:45

asper wrote:

UPDATE:
The problem seems to be under WIndows7 64 bit (maybe all 64bit WIn versions) because .elf files are compiling fine under Windows XP 32bit.
Client binaries work fine in 32bit and 64bit systems; I mean you can compile them under Win32 and they will work under Win64 and vice versa.
Here is a full r664 Windows release (.elfs+.exes+README+old bootloader
flashing guide)

Could it be possible, that libusb0.dll is missing in the package? (needed for flasher-OLD.exe)

asper · 2013-03-03 15:01:24

I used that package to flash so I don't think it's needed to flash with old flasher if your pm3 is correctly recognized by win.

Last edited by asper (2013-03-03 15:49:08)

asper · 2013-03-07 18:22:58

r672 compiled for Windows <-- compiled fine under Windows XP 32bit, works on Win7 64bit.

I still have perl problems under Win7 64bit (it compiles but no version number "injected" in binaries - see previous posts)

Last edited by asper (2013-03-07 18:26:23)

rule · 2013-03-07 21:35:38

I tried, but see no problem in Windows 7 (64-bit). Are you sure you downloaded the 64-bit version of strawberry-perl?

C0Y0-Ck3r · 2013-03-08 09:57:31

Everything is compiled well for me, but the problem I got is that when executing proxmark3 COM3 I got the proxmark3 prompt and when executing hw version nothing happens, it's like that the data is not sent to the proxmark. Any ideas why ?

rule · 2013-03-08 11:36:46

You are sure you have it connected to COM3 (check the device manager).
If you connect to a COM port that belongs to a different device, you will most likely get no any answer at all.

C0Y0-Ck3r · 2013-03-08 12:43:55

No its the good one, and the hw version worked one time, after that It wouldn't work

C0Y0-Ck3r · 2013-03-08 14:15:43

I think its ok, asper suggested to try it on a real and not on a vmware. I'll do that and the next tutorial will cover all the setup of the new firmware...

asper · 2013-03-13 19:34:09

Here is r679 FULL compiled for Windows.

Found the problem with perl under Win7 (maybe not only Win7, I think it can happens on other Win versions too) ! Here is my explanation of the problem:

i had a "bad path" for perl executable; the solution was going to path variable settings (look here where to go: http://www.computerhope.com/issues/ch000549.htm#1) and I put the perl folder path variable at the beginning of the path-line insted of at the end (so it's not a true "bad path" problem but probably windows looks for another perl.exe instead of strawberry one).

Now pm3 is compiling fine under Win7 64bit !

Last edited by asper (2013-03-13 23:31:50)

asper · 2013-03-18 20:46:18

Here is r681 FULL compiled for Windows.

Proxmark3 community

Announcement

#1 2013-03-01 12:34:31

Help compiling windows client

#2 2013-03-01 14:18:11

Re: Help compiling windows client

#3 2013-03-01 14:47:12

Re: Help compiling windows client

#4 2013-03-02 17:17:43

Re: Help compiling windows client

#5 2013-03-02 18:05:06

Re: Help compiling windows client

#6 2013-03-03 08:37:02

Re: Help compiling windows client

#7 2013-03-03 09:10:40

Re: Help compiling windows client

#8 2013-03-03 10:42:11

Re: Help compiling windows client

#9 2013-03-03 14:07:45

Re: Help compiling windows client

#10 2013-03-03 15:01:24

Re: Help compiling windows client

#11 2013-03-07 18:22:58

Re: Help compiling windows client

#12 2013-03-07 21:35:38

Re: Help compiling windows client

#13 2013-03-08 09:57:31

Re: Help compiling windows client

#14 2013-03-08 11:36:46

Re: Help compiling windows client

#15 2013-03-08 12:43:55

Re: Help compiling windows client

#16 2013-03-08 14:15:43

Re: Help compiling windows client

#17 2013-03-13 19:34:09

Re: Help compiling windows client

#18 2013-03-18 20:46:18

Re: Help compiling windows client

Board footer