> How are the FPC RTL documentations generated? I wanted to see if I could
generate .docsets files from them also.
A starting point: https://wiki.freepascal.org/FPCDocs_Tutorial
I believe that "write me" part is not far from calling make with certain
options.
--
Sent from: http://free-pascal-ge
I commented out all the try & except stuff and ran it.. I get this output:
Running
"i:\programming\pas-libusb_test_dll\src\examples\testopendevic_vidpid2.exe "
start
1
2
a05472131
a10CEEB93
b
c
FALSE 8086 10CE A36D EB93
FALSE 8087 10CE 0AAA EB93
FALSE 0424 10CE 2734 EB93
FALSE 1D50
Hi!
Am Samstag, den 17.08.2019, 16:16 +0200 schrieb Jean SUZINEAU:
> Le 17/08/2019 à 15:00, James Richters a écrit :
> > Function TLibUsbInterface.FindEndpoint(MatchFunc :
> > TLibUsbEndpointMatchMethod) : Plibusb_endpoint_descriptor;
> > MatchFunc(ED) is where the access violation occurs, but I c
Is the segfault in the same place or has it changed?
To debug further, you have to compare sizes of data structures, field
types and function call parameter types between the libusb 1.0 and the
old libusb0.1. - any mismatch could result in a segfault.
On 8/17/19 3:51 PM, James Richters wrote
Oops, I got mixed up.. it's usb.pas that isn't used anymore... I changed
LibUsb to stdcall and not it compiles again.. but I still get he access
violation with stdcall.
James
> from the copy of your github, looks like libusboop.pas has a uses statement
> for libusb.pas; so libusb.pas is stil
Le 17/08/2019 à 19:39, James Richters a écrit :
I think maybe it is the calling convention... First I tried to change
libusboop.pas (libusb.pas is the old unit, libusboop.pas is the one it uses) to
stdcall, I was unable to compile it, I get an error
libusboop.pas(1456,28) Error: Incompatible
fromt he copy of your github, looks like libusboop.pas has a uses
statement for libusb.pas; so libusb.pas is still used
https://github.com/Zaaphod/pas-libusb/blob/Hack/src/libusboop.pas (line 30)
Uses
Classes, SysUtils, LibUsb;
On 8/17/19 1:39 PM, James Richters wrote:
I think maybe it i
I think maybe it is the calling convention... First I tried to change
libusboop.pas (libusb.pas is the old unit, libusboop.pas is the one it uses) to
stdcall, I was unable to compile it, I get an error
libusboop.pas(1456,28) Error: Incompatible types: got "" expected ""
libusboop.pas(1726) Fata
Libusb can be compiled with either calling convention - one just has to
be sure which one.
In https://github.com/Zaaphod/libusbxhid/blob/master/libusbx.pas (line
35), the windows calling convention is stdcall and that apparently works
for both 64 and 32 bit windows. So, James' libusb10 dlls use
Le 17/08/2019 à 17:10, Stefan V. Pantazi a écrit :
The obvious first thing to make sure is that the calling convention
matches the library for the platform. I see that in
https://github.com/Zaaphod/pas-libusb/blob/Hack/src/libusb.pas 9line 46)
the calling convention on Windows is cdecl (the stdc
The obvious first thing to make sure is that the calling convention
matches the library for the platform. I see that in
https://github.com/Zaaphod/pas-libusb/blob/Hack/src/libusb.pas 9line 46)
the calling convention on Windows is cdecl (the stdcall is commented
out). In libusbxhid, if I remember
How are the FPC RTL documentations generated? I wanted to see if I could
generate .docsets files from them also.
Regards,
Ryan Joseph
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listi
Le 17/08/2019 à 15:00, James Richters a
écrit :
Function
TLibUsbInterface.FindEndpoint(MatchFunc :
TLibUsbEndpointMatchMethod) : Plibusb_endpoint_descriptor;
MatchFunc(ED) is where the access
vi
I’m trying to figure out why I get an access violation when I try to open my
device with pas-libusb but it works with libusbxhid they both are using
libusb-1.0.dll
I put a bunch of hacks into pas-libusb to try to figure it out… just a lot of
writeln’s so I can try to track down exactly what
> Several people have already looked at it, but it's a complex issue that
> is not yet understood.
>
> Jonas
Ok, thanks.
Hope all those people didn't find anything secret forcing them to remain silent
with regards to bug comments :)
-- Regards,
Denis Golovan
On 17/08/2019 12:10, denisgolovan wrote:
> Could somebody look at https://bugs.freepascal.org/view.php?id=35877 ?
> Latest fpc trunk is completely broken while using generics.collections.
Several people have already looked at it, but it's a complex issue that
is not yet understood.
Jonas
___
Hi all
Could somebody look at https://bugs.freepascal.org/view.php?id=35877 ?
Latest fpc trunk is completely broken while using generics.collections.
-- Regards,
Denis Golovan
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
https://lists.fre
Dear specialists,
I have fallen in to complex issue and I do not know how to solve that. I
can make myself happy thanks to Pandroid and his author, because I can
create, modify some really functioning apps for myself. But when I will
create some app myself completely from scratch and if I would
18 matches
Mail list logo
