I am trying to build a static library (foo) that uses functionality from another library (bar).
Example:
void foo::f1()
{
bar::b1();
}
Unfortunately, when using foo in some of our projects (requiring us to link with bar as well to support foo), exports from bar are conflicting with other libraries. Is there a way to import bar when building foo without also exporting bar's functions? I would simply like the compiler to build foo by in-lining b1() into the implementation of f1(). Then when we use foo in our project, hopefully the compiler will not even need to know about bar, and won't generate conflicts.
I was hoping this is what "Link Library Dependencies" in the foo project settings would achieve, but no such luck.
For reference, it is multiple definitions of common WinCE "bridge" functions from different libraries that are giving us trouble in our exe project.
Thank you for any assistance.