While the 32 bit version of libpython34.a can be unzipped from the www.sigrok.org/tmp/Python34<32 bit version>.zip file, the 64 bit version is not in the www.sigrok.org/tmp/Python34<64 bit version>.zip file. These files are used to build the 32 and 64 bit versions of the sigrokdecode libraries. I looked in the Windows 64 Python install and didn't find it there either.
I did try using the mingw32 dlltool utility to make an import library from the python34 DLL and that allowed me to complete the 64 bit build of pulseview. I have as yet been unable to get pulseview working with the DSLogic, even with the nightly. I installed the firmware files using the script, and I have workewd with Zadiq, but no work. The DSLogic works OK with DSView, so I no there are no hardware issues.
Yup, I've been experimenting with adding the missing .a as well recently, merged that part into the script now. However, it's not fully working. There seem to be issues there still, haven't investigated yet, though. There's a prebuilt 64bit installer now at sigrok.org/jenkins, can you please try that one and see if it works for you (i.e., if you can successfully run decoders)? Thanks! Also, maybe you could have a look at the recent sigrok-cross-mingw patch, maybe I've missed some important step there?
I have looked some at this. I have my own builds of 32 bit release, 32 bit debug, and 64 bit release. I also have a recent nightly build. My builds were all successful with the new script. I have tested all these builds using an 8bit logic clone, since that is sort of the lowest common denominator of logic analyzers, and one of the earliest. All builds work satisfactorily in base modes. I have not yet tried the decoders, as I have not put up a suitable signal, but I will do so soon.
This is a duplicate of #1195 (there would be 4GB allocations for no obvious reasons and protocol decoders wouldn't work at all). The issue has been fixed in the mean time and decoding works fine on 64bit Windows. The way libpython34.a is generated by sigrok-cross-linux is thus also correct and working. *** This bug has been marked as a duplicate of bug 1195 ***