KitsunePrefecture
Dear @Pairisto ,
Have a further successful journey as C++ developer
and possibly join us as a future Haikunaut as well !
Kudos !
Dear @Pairisto ,
Have a further successful journey as C++ developer
and possibly join us as a future Haikunaut as well !
Kudos !
Well done so far, congrats on the progress!
Nice to see! Great work!
Hi, nice work indeed
A quick question, I am testing with Indy10 on Lazarus, specifically (for example) with test project idHL7 which creates a client and server and tries to communicate with each other. This works nicely on Windows, Linux, but not haiku (tested x64).
From the test event messages written at the bottom of the testapp window, it looks like cliënt messages work, but not server messages.
Also I am testing with our companies app, which fully works ok, except for its Indy10 tcp server. A client on i.e. windows can connect to the server, but the server is totally unaware (no messages come through to it).
Linux arm and x86, and windows x86 and x64 are all ok.
Would be cool if this apparantly haiku specific problem could be solved …
Btw this problem exists for some years already at least.
Again, don’t know if this would be of any help or if it’s the same problem. I just thought I’d mention it.
Thanks again!
So this is normal, on haiku only the first line (Clientconnect) appears.
Oh yes; in order to compile you will need to add a few missing defines in Indy, I think ipv6 specific by heart in files idstackconsts.pas and idstackunix.pas. these should be known in haiku but apparantly aren’t.
1 replyDefines:
Ipv6_join-group,
Ipv6_leave_group,
Ipv6_unicast_hops,
Ipv6_pktinfo,
Ipv6_hoplimit,
And in the Unix file
Msg_nosignal isn’t found.