Some findings on the same. On PC, linux, build with RELEASE=1, the compilation is done with *'-Os' - Optimize for Size.*
For Yocto, even with RELEASE=1, there are no Optimization flags and is build with '-g' to allow bitbake pick up the debug symbols. Adding '-Os' to yocto builds along with -g, the sizes are comparable. Any undesired effect because of this? -Ravee On Wed, May 9, 2018 at 11:46 AM, Raveendranath Kondrakunta < [email protected]> wrote: > Hi, > > IoTivity build for PC x86_64: size of liboc.so is roughly ~500K > IoTivity build for ARM 64 with Yocto: size of liboc.so is roughly ~5.9M > > In both cases, the the symbols are stripped off the libraries. > > When I did readelf on the libraries for PC an ARM, the arm version has > lot _ZN5boost6detail7variant symbols, while on PC version, they are present > in very less number. > > Anyone has similar observation? > > -Ravee >
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
