• Dan Mihai's avatar
    [IOT-2011] linker changes for oc_logger · f8af7607
    Dan Mihai authored
    Windows currently has several different copies of oc_logger code and
    data in a single process. Other platforms are using a single copy of
    shared library oc_logger, in each process/app.
    
    It's better to avoid differences across platforms, because otherwise
    changes tested on one platform might not work on the other platforms.
    
    Linker behavior unchanged by this patch:
    ----------------------------------------
    
    1. On non-Windows platforms: IoTivity sample apps, and apps outside
       IoTivity, link with oc_logger.
    
    2. On Windows: IoTivity sample apps, and apps outside IoTivity,
       continue to link with octbstack.lib.
    
    Linker behavior changed by this patch:
    ----------------------------------------
    
    1. On all platforms: IoTivity internal tests link with the static LIB
       oc_logger_internal.
    
    2. On Windows: IoTivity sample apps, and apps outside IoTivity,
       no longer link directly with oc_logger.lib. They obtain access to
       oc_logger APIs by linking with octbstack.lib.
    
    3. On Windows: Octbstack.dll links with the static LIB
       oc_logger_internal, and exports public oc_logger APIs.
    
    Change-Id: I3ca36ffcbebea7822918998ac3fced1c5071726e
    Signed-off-by: default avatarDan Mihai <Daniel.Mihai@microsoft.com>
    Reviewed-on: https://gerrit.iotivity.org/gerrit/18769Reviewed-by: default avatarTodd Malsbary <todd.malsbary@intel.com>
    Tested-by: default avatarjenkins-iotivity <jenkins@iotivity.org>
    Reviewed-by: default avatarMike Fenelon <mike.fenelon@microsoft.com>
    f8af7607
SConscript 3.27 KB