Original Post
I was just wondering why its not possible to link other .libs when building another .lib file. For example, at the moment im playing with collada, and using the DOM librarys, which can either be built into a .lib or a .dll. Using the .dll DOM build method, you build with all of DOM's external .libs/headers, and compile to that one .dll. And then in the client project, you just link with the DOM.lib / headers when building, and include the .dll with the .exe. Whereas with the .lib DOM build, you compile with all the DOM external headers, and build. But in the client app, you have to include the DOM.lib/headers AND the DOM external libs/headers. So, when creating a wrapper of .lib A, and compiling this to .lib B, why cant you link .lib A into the project of .lib B, thus not requiring .lib A in a client app, just .lib B. You seem to loose the linking option tab in vs2008, when building a .lib project. hat are the reasons for this? Thanks