Zadig
I found a way to make my test with libusb-win32 work. You just need to install a specific driver for the usb device you want to see.
This can be done using Zadig ( https://zadig.akeo.ie/ ). If you change the driver to "libusbK" or "libusb-win32" for a certain device with Zadi
I've forgotten to give the command line to compile (change
"C:\lazarus\fpc\3.0.4\bin\x86_64-win64" to your fpc installation):
C:\lazarus\fpc\3.0.4\bin\x86_64-win64\fpc.exe -MObjFPC -Scghi -O1 -g -gl
-l -vewnhibq -Filib\x86_64-win64 -Fu..\pas-libusb\src -Fu.
-FUlib\x86_64-win64 -FE. -olsusb.exe
I've made another (unsuccessful) test, using libusb-compat (
https://github.com/libusb/libusb-compat-0.1/wiki ).
It's a compatibility layer which allows to use the new libusb
1.xx through the old API of libusb 0.1
I get nearly the same results as with libusb-win
I tried to make an import for libusb-1.0.22.7z from
https://libusb.info/ .
The import unit is very buggy but I could make a small program to
list the usb devices.
On my machine, it gives the same results that the example program
libusb-1.0.22\examples\bin64\
With libusb-win32 I tried to make a small program to list the usb
devices.
I discovered that the constant PATH_MAX had changed from 4096 in
pas-libusb to 512 in libusb-win32-bin-1.2.6.0\include\lusb0_usb.h
line 21 . This was causing an exception.
Now the prog
Mgr. Janusz Chmiel schrieb am Sa., 3. Aug. 2019,
11:48:
> Many of advanced users and developers have tried PPCJVM. It is really
> possible to create fully functioning Android applications. And because
> it is even possible to access methods from previously compiled .jar
> files including Mysql.ja
Many of advanced users and developers have tried PPCJVM. It is really
possible to create fully functioning Android applications. And because
it is even possible to access methods from previously compiled .jar
files including Mysql.jar and others, Pascal language have very big
potential.
But it
