Just to make clear: The LazMapViewer package itself is self-contained, it exposes all functionality needed based on standard classes: the download is done by fphttpclient, and rendering is done by LazIntfImage - there is need to install the other packages. The add-on packages were motivated by user request or the history of the original mapviewer component, they provide alternative components to be hooked in for download (synapse) and rendering (RGBAGraphics oder BGRABitmap). It only makes sense to install these packages if the default behavior is not enough, and in fact, I do not see much difference, and rendering with BGRABitmap even seems to be worst of all (maybe/certainly the code can be improved - help is appreciated). Of course, for the add-ons the related packages must have been installed first.
GetMem, is there a way to control the behavior of OPM for this situation? AFAIK, all the sub-packages are checked in OPM for installation when the top-level checkbox is marked. I would prefer to have only LazMapViewer.lpk checked by default and leave the add-ons unchecked to indicate that they are not absolutely needed and do not provide new functionality.
dbannon, I am not sure if the ssl_openssl.pas and ssl_openssl_lib.pas units are correct here. AFAIK, they are not contained in the laz_synapse package, but needed for ssl access by synapse. I think the duplicate unit message occurs because you have these units somewhere else. Try to delete the units in the mapviewer installation, and the compilation should work (not tested). A package not containing all units required easily leads to this mess.
dbannon, I would appreciate if you could have a look at the usage of ssl in the standard package (unit mvdlefpc). I think it has the same issues that you reported for the corona program.