Investigate Binary Size Overhead of Linking to Wrapper (Boost)

[planetchili]

Concerns have been raised over the dependency of the Wrapper on some Boost libraries. The wrapper has minimal dependency on CommonUtilities, part of which uses Boost libraries (such as ASIO). However, the Wrapper does not consume any objects that have these boost dependencies, so the dependency should not result in additional size of final target binary that links to Wrapper.

Perform a basic experiment where a Release binary size is compared linking to and not linking to the Wrapper to put an upper limit on the maximum that Boost could potentially be contributing. In the non-linking case, add replacement functionality to compare more realistically.

[planetchili]

Checked Release config .exe size for a minimal app that includes the majority of the wrapper (session open, introspection, register dynamic query, track target, poll dynamic, cleanup) and compared with size of a basic hello world, as well as a simple 200 LOC app that uses most of the same basic C++ building blocks as Wrapper (vector, string, unordered_map, etc.). clang-cl was used.

Scenario	Size
General Wrapper	564kB
Hello World	264kB
C++ Basics 200	461kB

[planetchili]

Test project at: https://github.com/planetchili/ipmvcpkgtest/tree/exp-size