(10-29-2018, 11:08 PM)Cirrus22 Wrote: It appears than anything with the FMX Forms unit in it blows up the application with the DYLIB with "Could not Register TFMXApplicationDelegate".
That is something that needs to be taken up with Embarcadero. The only issue I see in Quality Portal that is related to TFMXApplicationDelegate is RSP-18580: Firemonkey applications don't terminate normally on macOS.
(10-29-2018, 11:08 PM)Cirrus22 Wrote: when I queried them about using it in a DYLIB actually told me they doubted that you could use FMS application / DYLIB (actually, I though that was the whole point of FMX, maybe I should just look at some other language)
FMX can consume, and create, dylibs for OSX. Just because the TMS folks didn't test it doesn't mean it can't be done at all.
(10-31-2018, 06:34 PM)shochberg Wrote: For the Windows (VCL) version using XE5, I originally seemed to need to include ssleay32.dll and libeay32.dll with the app but it now does not seem to be necessary with Tokyo. Am I correct?
No. The DLLs are still required. If you are not deploying them, Indy is likely loading them from elsewhere on your system's DLL search path.
(10-31-2018, 06:34 PM)shochberg Wrote: And is that because IdSSLOpenSSL is now automatically added to the form when IdSSLIOHandlerSocketOpenSSL is added?
No, that is not why. And besides, the IdSSLOpenSSL unit is the one that actually implements TIdSSLIOHandlerSocketOpenSSL, it should have always been getting added automatically regardless. Maybe you are thinking of the IdSSLOpenSSLHeaders unit instead? Doesn't matter, the DLLs are still required nonetheless.