I apologise if this is a trivial question. I have looked in the documentation (the PDF is copyrighted 2006 so I am unsure of the currency), done the usual web searches, stack overflow etc, but nothing definitive. There are numerous parts of the documentation that say:
I'm note even sure what that means.
Regardless, I have a third party component that uses Indy. I have asked the vendor whether it is cross platform. His advice is that 'his' code is cross platform, but he uses INDY and INDY is not cross platform. INDY uses
To which I replied:
To which he replied:
So I have been having a discussion with a vendor who is simply a user of INDY and I don't think he quite has all of the knowledge. Further, whilst his code might work with FireMonkey, it will only do so in Win32 mode, he uses Registry and other windows dependent units AFAICT.
Regardless, and so my (apologetically trivial) question: Is INDY (latest version) Cross Platform, ie. can I use it in my application that is to be deployed on macOS? and if so, is there anything 'special' I would need to do?
For the record, his USES clause contains these references to INDY components:
IdHTTP,
IdLogFile,
IdComponent,
IdSocks,
IdSSLOpenSSL;
Quote:Additional code changes may be required to maintain cross platform compatibility, as discussed in previous sections.
I'm note even sure what that means.
Regardless, I have a third party component that uses Indy. I have asked the vendor whether it is cross platform. His advice is that 'his' code is cross platform, but he uses INDY and INDY is not cross platform. INDY uses
Quote:The component is not compatible with Firemonkey as it uses DLL files form Indy and the DLLs aren't cross-platform.
To which I replied:
Quote:According to StackOverflow, INDY works with FMX (and in my case macOS) and has for some time. Since there is nothing visual the VCL doesn't get invoked (this is from 2011).
Quote:Indy ships with the IDE (and has since D6) so there is nothing extra to buy if you already have XE2 installed. Also, Indy is open-source, so you can upgrade an Indy installation using source code from Indy's public access SVN server or mirror.
Regarding FireMonkey, Indy does work in FireMonkey. Indy uses whatever the native socket API is on a given platform (WinSock on Windows, Posix on Mac, libc on Kylix, etc).
The only known gotcha with Indy under FireMonkey at the moment is the TIdAntiFreeze component is not available at design-time. The IDE cannot resolve it correctly due to the non-standard way it is packaged (to be adressed in Indy 11). You can instantiate it programmably in code at run-time, though.
To which he replied:
Quote:Indy works with Firemonkey, although the 2 DLL files included (ssleay32.dll, libeay32.dll) aren't cross-platform.
So I have been having a discussion with a vendor who is simply a user of INDY and I don't think he quite has all of the knowledge. Further, whilst his code might work with FireMonkey, it will only do so in Win32 mode, he uses Registry and other windows dependent units AFAICT.
Regardless, and so my (apologetically trivial) question: Is INDY (latest version) Cross Platform, ie. can I use it in my application that is to be deployed on macOS? and if so, is there anything 'special' I would need to do?
For the record, his USES clause contains these references to INDY components:
IdHTTP,
IdLogFile,
IdComponent,
IdSocks,
IdSSLOpenSSL;