With reference to the answer to Linking a static boost build into a static library under VS2012 & Win32/64:
In essence I have produced a library, A.lib, which is dependent on another of our internal libraries, B.lib, as well as the Boost libraries libboost_system-vc110-mt-gd-1_51.lib and libboost_filesystem-vc110-mt-gd-1_51.lib.
Now, my colleague on another team is using my library, A.lib, and as I would expect from reading the aforementioned answer, he gets a linker error because he does not have the boost library in his linker path.
I solved the issue by simply packaging the particular boost library in the same folder as A.lib.
However, what puzzles me is that this actually seems to work. Why does the linker not complain about B.lib missing?
B.lib is built by yet another team (and I do not have access to the source code), so in my mind linking to that should be equivalent to linking to a boost library.